More often than not, when I restart Robot-C, the Joystick window ends up somewhere off-screen (bottom-left). It seems the default location is not setup for lower-resolution screens. Is the location hard-coded, and can it be brought back up 'higher' on the screen. Better yet, can it remember where it was last time and go there again.

Solving this usually requires me to start the debugger, 'disable' the Joystick button, and then I have to stop/restart RobotC from scratch.



Nate

I too have seen this recently.

You can correct it by driving the system menu with the keyboard and so move it back on screen. I think the right sequence of input is the following:
* Alt-space
* M (for 'Move')
* Up arrow (to select the top window edge; other arrows work similarly)
* Use arrow keys or mouse to position the window.

Thanks Bob, I'll try that next time.

We have an option for this inside of ROBOTC, actually:

Window -> Menu Level -> Super User
then...
View -> Delete All Saved Window Positions

ROBOTC will close and wipe out all of the window positions, including debugger windows, for the next time you run ROBOTC. The defaults will be restored (which means they'll show up on your smaller screen!)

My students have been running into this problem a lot with v3.x of ROBOTC as well. The solution above (using the keyboard to move the window) doesn't really work as I can't seem to get focus on a modal window off the screen. Using alt-tab doesn't target the modal windows within ROBOTC, just the running IDE itself.

As for the menu option to clear the window positions... we've been using this, but it is a pain since it forces you to close & re-open the IDE.
I would prefer a solution that could reset the position without relaunching the IDE or better yet, find a way to keep the IDE from launching windows off-screen in the first place.

Because the window positions are stored in the registry, that would actually be a larger change to ROBOTC since those values get loaded when ROBOTC opens and they get saved when ROBOTC closes (hence why if ROBOTC crashes, it doesn't remember your changes)

It's something we can improve in the future for sure, but there isn't any "easy fix" at the moment.

Thanks Tim, I'll try this now!

My team has been seeing this issue annoyingly often in 3.x as well.

Tim, this is happening when we close the IDE cleanly and has nothing to do with it crashing. The IDE seems to almost randomly re-open previously closed windows off the screen which were never moved off screen.
MHTS just reported the same issue in another thread and I think there is enough reports of it in this thread and others to be investigated as a bug?

We have begun investigating this. We are planning another update for sometime in November, so I can assure you this will be fixed by then.

Thanks everyone!

That's great to hear & thanks for such a quick response!

Any update on this? November is almost over.


Nate