Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SM Explorer main window disappears occasionally #79

Closed
arejaw opened this issue Jul 24, 2018 · 6 comments
Closed

SM Explorer main window disappears occasionally #79

arejaw opened this issue Jul 24, 2018 · 6 comments
Assignees
Labels

Comments

@arejaw
Copy link

arejaw commented Jul 24, 2018

Hello!

I don't know what causes it, but I fairly frequently do 'something' whereby I 'lose' the main SM Explorer window. When this happens, the JKI SM Explorer option is not available to relaunch b menu or the CTRL-J hotkey.

Closing the BD and then CTRL-E brings the BD back again, but not with the SM Explorer. I need to close out of the VI, and sometimes LV.

Is this known or something I should be tracking down on my system (background/tray programs, for example)? I waited until I upgraded to 2018 before reporting, hoping it might go away.

Thanks. The SM and SM Editor are awesome, I appreciate your continued efforts supporting both, and providing them to the community (among many other utilities you provide).

Randy

Windows 10, LV2018 Pro
JKI State Machine Editor v2013.6.3.241 by JKI
Released On: Tue, 19 Jun 2018 22:20:34 -0700

@jlj-ee
Copy link

jlj-ee commented Dec 5, 2018

@arejaw I have also experienced this behavior on occasion on Windows 10/LV2016, at least with the separate State Machine Editor installation. Keeping an eye out for it in the new 2018 release of JKI State Machine that now includes the editor with it.

@jimkring
Copy link
Contributor

jimkring commented Dec 5, 2018

@arejaw this issue was (hopefully) fixed in release 2018.0.2.37. You can open VIPM and it should alert you to the new version (or you can find it in the package list). Please let us know if that helps.

@arejaw
Copy link
Author

arejaw commented Dec 6, 2018

I have not had this occur with the new versions (I'm now using 2018.0.2.38), where I've had to exit Labview to recover so far - thanks!

There is some odd behavior with the SM Editor windows visibility, though. Not a big deal, but FYI:

On dual monitors, one with the FP open and the other with the BD open:

  • minimizing the BD works as expected...both the BD and SMEditor minimize. And activating the BD again returns both in the previous locations.
  • however, first minimizing the FP and then the BD leaves the SM editor window visible on the Desktop. Then maximizing the BD works fine - SMEditor and BD return to their previous locations. If one next activates the FP window, the FP returns properly, but the SMEditor disappears. Simply clicking on the BD brings it back though, so not really a big issue...i.e., it's not crashed.

Thanks for all the huge improvements in this new fall release - really like it.

jimkring added a commit that referenced this issue Dec 6, 2018
…ar occasionally

Changed all the dialogs (which are launched asynchronously) so that they open their own JKI SM object reference during "Data: Init" and close their reference in "Data: Cleanup"

@jimkring
Copy link
Contributor

jimkring commented Dec 6, 2018

Fixed in JKI State Machine Release 2018.0.4.39. Available for download and install with VIPM.

I was able to work around this issue. The problem seems to happen when the FP is already minimized, then the BD gets minimized and there are no other VIs' FP or BD open, so there's no VI Activation event that gets triggered when the target BD is minimized (there's no other VI that's active). I was able to work around this by adding a test in the Timeout frame to see if the target BD is minimized, and then will set the JKI SM Explorer window to Hidden.

Please excuse the sloppy code:
image

@jimkring jimkring closed this as completed Dec 6, 2018
@jimkring jimkring self-assigned this Dec 6, 2018
@jimkring jimkring added the bug label Dec 6, 2018
@arejaw
Copy link
Author

arejaw commented Dec 6, 2018

Awesome, thanks again Jim (also for fixing the Find Callers issue this morning with x.39).
It's working great, including both dual and single screen, too. I work a lot on a remote machine with only one monitor so have the limited screen space; windows mgmt turns out to be esp important (esp for these old eyes).

@jimkring
Copy link
Contributor

jimkring commented Dec 7, 2018

@arejaw you're welcome! I was able to reproduce/fix/test the issue on only a single screen, so I'm glad it's working on dual screens, too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants