An option for remembering the last window position and placing the window there on re-connect would be nice.
Logged In: YES
Chicken assumes that you want a new window to be either as
large as the screen you're viewing, or as large as your
monitor, whichever is smaller.
I'm not sure how to reconcile the two preferences clearly.
I guess it would have to be a user preference. Any
suggestions on what the actual behaviour should be?
Example: If the new window is smaller than the screen or
its size has been changed by the user, use that size next
time, otherwise make it as large as possible. Use the
preferences to reset the behaviour.
It's nasty and would confuse people. I'd like a cleaner way
of implementing it before I do anything.
Logged In: YES
The situation I have is the screen I am viewing is (much) smaller than my monitor, so I like it down at the bottom corner of the screen so I can see it while in other apps.
The way that I think would surprise me the least is if "remember position" is checked and size of local desktop hasn't changed and size of remote screen hasn't changed then place it at the last saved position; otherwise place at 0,0 maximized as it does now. Basically make it very conservative and only use the old position and size if it looks like absolutely nothing has changed about the setup.
But that's just me and I'd definitely be open to other ideas on what good behavior would be.
That seems reasonable. Do you envision this being a
checkbox in the connection dialog, or a
checkable/uncheckable menu item that you can set while
connected? Or something else?
Maybe a combination of both? A checkbox in connect would be nice since you can override it when making the connection to not get the saved position. But I really like OmniWeb's explicit "Save window size" menu item as opposed to IE's take the last window open's size (which may have been a tiny popup ad) automatically.
So I'd lean towards a "Save window position" item in the Edit menu (no toggle) and then a "Use saved position" checkbox when connecting (which remembers its state like the remember password and allow sharing ones).
Okay, I'll add this for the next feature-enhancing revision.
Logged In: YES
My situation is that I need to use VNC to connect to a WinXP box in order
to access a courier dispatch site that only renders properly in WinIE. I
keep a large window open on the Mac that is focused on the lower-left
corner of the XP screen and displays the browser. This window is
frequently obscured by other apps (both on my Mac and on others' Win
boxen), so there is a flashing dialog that appears in IE and rings a bell to
alert you to a new job in the queue. VNC doesn't transmit sound, and
obviously the dialog won't come to the front of the Mac windows, so I
opened a second connection to the same box and shrunk that view down
to the size of the dialog and focused on the area in which it would
appear. I placed this window in an unused corner of my desktop and
now the flashing of the dialog alerts me to the fact that a new job is in
the queue and needs to be acknowledged. I named the first connection
Polaris (the name of the dispatching system) and the second connection
Polaris Alert, and used the Set Connection Title option to title the
windows Polaris and Polaris Alert. Everything was working wonderfully
until I had to quit CotVNC. When I reopened the two connections, both
windows were titled Polaris Alert and obviously, they were full screen
and had to be readjusted.
I suggest creating a Window Prefs section in either the Connection or
Connection Profile section. This would allow you to set a custom title for
the window and a checkbox to "Save window size and location." This
checkbox would enable a button that snapshots the current state of the
window. If the user leaves the box unchecked (default) the window for
the connection would continue to behave as it does now. I'm thinking
that this pref would be better-suited to the Connection itself, but
whatever works. The custom window title could be an checkbox-option
itself, with the default (unchecked) simply using the name of the
Connection in the Servers list.
serversurfer, if you're comfortable doing so, you may want to build the
current version pulled from CVS. I think it'll do what you want properly if
you bookmark your connection twice in the Connection dialog with the two
different names you want.
Resolved for Chicken 2.0b3.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.