XnView "Hypervisor"
Posted: Wed Aug 06, 2008 7:45 pm
Much of the functionality wished for XnView is already available if you turn off "Only one Instance" and run with multiple XnView sessions on the desktop.
For instance, I wish for side-by-side browsers in a single tab a la TC. Well, tiling two XnView browsers on the desktop accomplishes nearly the same thing, doesn't it?
The problem is that those two XnView sessions don't know each other exists. The user has to use system desktop functions to tile them. There is no way for one session to report data to the other session, for instance, such as adding categories in one session and having them show up in the other session without the user performing a restart or refresh. Etc.
Furthermore, when allowing XnView to run with multiple sessions, opening an image file (associated with XnView) from Explorer or another file manager automatically opens a new XnView window, instead of adding the image to a new tab in one of the XnView sessions.
So I always run with "Only one Instance" checked, in order to avoid too many simultaneous XnView sessions. Which means I can't make use of the side-by-side functionality available when two (or more) sessions are open.
My idea is for an XnView functionality one might call the XnView "Hypervisor" which would control the behavior of separate simultaneous XnView sessions.
The Hypervisor could open/close Xnview sessions, tile designated sessions (according to user defined schemae), manage/assign/synchronize INI data between sessions. Control which session is the "go to" session when opening an associated image into XnView. Etc.
I visualize a new XnView menu item that would open a dialog which would list/open/close sessions and from which the various actions would be controlled...
For instance, I wish for side-by-side browsers in a single tab a la TC. Well, tiling two XnView browsers on the desktop accomplishes nearly the same thing, doesn't it?
The problem is that those two XnView sessions don't know each other exists. The user has to use system desktop functions to tile them. There is no way for one session to report data to the other session, for instance, such as adding categories in one session and having them show up in the other session without the user performing a restart or refresh. Etc.
Furthermore, when allowing XnView to run with multiple sessions, opening an image file (associated with XnView) from Explorer or another file manager automatically opens a new XnView window, instead of adding the image to a new tab in one of the XnView sessions.
So I always run with "Only one Instance" checked, in order to avoid too many simultaneous XnView sessions. Which means I can't make use of the side-by-side functionality available when two (or more) sessions are open.
My idea is for an XnView functionality one might call the XnView "Hypervisor" which would control the behavior of separate simultaneous XnView sessions.
The Hypervisor could open/close Xnview sessions, tile designated sessions (according to user defined schemae), manage/assign/synchronize INI data between sessions. Control which session is the "go to" session when opening an associated image into XnView. Etc.
I visualize a new XnView menu item that would open a dialog which would list/open/close sessions and from which the various actions would be controlled...
