However, every time I close the application and later reopen it, I have to span the two monitors (which is trivial, with the special icon that UltraMon provides on the title bar), split the screen vertically (trivial), and then position the mouse on the vertical bar that separates the two windows (code and preview) and slide it to make sure it is in the left monitor window so that a few characters of HTML and content don't spill over into the right window.
Gosh, it would be nice if an .ini file would record this at application exit time and reapply it when the application is restarted.
Don't know if this made it somewhere on a list, but i would also like the functionality of starting on the same screen where i closed rapid php from. I also use a dual screen workplace and use rapidphp on the 2nd screen, but it alway's starts maximized in the first screen.
Alas, I've "graduated" to WeBuilder 2008, but still have the same issue: there is apparently no *.ini file that remembers the screen configuration from the last time the software was closed. I could find no setting for this in Preferences, so ....
Don't use WeBuilder 'maximised', but in its resizeable state. Position as required. Close via ALT+F4. Reopen. Does it remember the position? It does on my laptop.
This is with v9.1.98 - what version are you using?
In the registry, there are position values, so they should be remembered.
I would suspect the same will be with other apps - RapidPHP, etc.
On my machine, using Vista Business and WeBuilder 2008 (build .100) I can position the editor anywhere on the screen, at whatever size while 'half-maximised', and when I close it using 'File > Exit', or the 'X' in the top-right corner, it remembers exactly where it was on the screen when I reopen it, as well as file(s) I had loaded, the cursor position at exit in the active open document and the scroll-bar position.
I cannot confirm on dual monitors as I don't have that set up, but I imagine if it remembers the position of these other aspects (as chrisjlocke points out, there are registry entries for such things, which means the software is set up to actively 'remember' WeBuilder's state at exit) then logically it should remember dual screen positioning as well.
I can't explain why WeBuilder does not exhibit this behaviour on your machine. Do you run any registry cleaners or other 'security/utility' type software? Often these tools remove MRU-related data like this so they can 'prove' they are doing something, ignoring the fact that often we like to be able to easily 'Open Recent Files'.
The point is that WB is equipped and set up to remember all these details on close; except, maybe, the dual-screen positioning thing, (which would be cool to get working for those who use it, if it doesn't already) so it *should* do it on your machine. If not, then something is messing with your registry settings and/or preventing those values being saved when WB closes.
