Shame on you guys - just kidding :-)

Wonderful program, but just ran into something that should be easily fixable.

If I open SQLyog, resize and position it, "thankfully", the next time I open it, it will be in the same position and same size; however, this can cause a major problem when using multiple monitors.

Often times when using my laptop, I have a second monitor attached with the desktop "extended" to the second monitor. I'll place SQLyog on the second monitor. BUT, if I forget to drag it back to the primary monitor before closing, AND, the next time I open SQLyog and the second monitor is NOT present - guess what. It is not visible and there's practically no way to get it back except find and connect the second monitor.

For my programming, I use a FOSS language (ooRexx) that includes an ooDialog "tool kit". One of the methods of this tool kit is "ensureVisible", which is designed for the exact problem described above. Once a dialog is display, the method determines if it is visible on the "current" display configuration - if it isn't, it will "gracefully" decrease the X & Y positions until it is visible. If, it'd be of any help I'm sure I can track down the Windows API used by this method.

Lee

Sorry, broke the cardinal rule of not specifying version in use.

SQLyog Enterprise - MySQL GUI v5.25

Peter, I posted the following question to the ooRexx Development team
Does the "ensureVisible" method of ooDialog use a Windows API to accomplish its goal or is this pure ooRexx code?

And here is the response I just received.
It uses a Windows API. What is done is that the DM_REPOSITION message is sent to the dialog window. This is a dialog specific message, not a general window message. (DM_ -> dialog message as opposed to WM_ -> window message.)
When a dialog gets this message it repositions itself so that it is completely on the screen (if it needs to.)


Hope this helps

Lee

Yes, your are right!

When we open the program we do not check if the coordinates stored are available.
I do not know exactly how to do this, but there must be a way!


I added this issue here:
http://code.google.com/p/sqlyog/issues/detail?id=433