Titles and buttons.... picky is me.

[NightRyder]

Maybe cuz I'm dumb.. but the properties should have titles, and links to the other properties page.

Since the properties were split, I think they should have defining titles on the window that opens up, and a button to link to the other set of properties.

Also, maybe I'm being picky, but I feel the buttons "cancle, ok and apply", should be in a more normal order. ie, "ok, cancle and then apply" (left to right). Thats the way windows usually has them setup (display properties comes to mind). maybe this is the normal way for some other system, and if so, well, It's fine as it is anyways.

[Rudi De Vos]

ok/cancel/apply: Layout was fast made to test functionality.
We need to clean it up.

Titles: OK
links: no, The admin properties should normal only be used onces, when the sysadmin sets them.
The idea behind the split was to have a set of user and admin properties.

Possible some properties are on the wrong page.
Are there admins that should be on the user or invers

Thanks for the feedback, thats the reason it is called TEST19

[NightRyder]

I'm thinking the 'default screen scale' could be put in normal props and the 'share this window only' might want to be put on the admin page.

I'm not sure what the 'share only' does, but it sounds like it would force the viewer to watch only one window, and that should be an admin only thing.

I'm assuming that the admin would be the person showing or configuring the station, while the normal user would just login and check things out... but maybe I'm wrong.

Now that I think about it, is 'share this window only' the same as the 'select single window' button on the top toolbar? Does this option make you only look there, and you cannot look elsewhere. Maybe usefull in a student teacher setting? That seems like it should be admin only, unless there is a totally different use.

The default screen size might be abused if it sets it for all users, but if it can be a different setting for each user, then it should go into the normal properties.

[An Interested User]

I see two uses for this: administrative server-side limitation of access (as you are discussing), and user client-side use (to limit bandwidth usage when working over a slow connection). In the latter case, the user may open a window, switch to single window view on that new window, work with it, then later switch back to do something else. I can see both arguments, as I have uses for both.

However, to handle both situations, you would need to have a server-side override. i.e. If the server limits access to a single window through administrative settings, then the client cannot switch to "share screen".

On the other hand, this might be moot if Ultr@VNC already handles both situations...