On 26/01/11 9:27 AM, Igor Stasenko wrote:
UIManager, during image startup, checks if image runs headless, and if
so, then it switching to non-interactive mode.
The non-interactive mode means that any request to UI manager which
normally leads to some user interaction now will trigger an error
(ErrorNonInteractive).
If you run image headful again, it will switch to usual UI manager
back, so don't expect to have this error when running headful image.
And be careful when testing/writing your code: image will run using
different ui manager depending on startup conditions.
This is great work!
I will test it out shortly, but I'm wondering about the VNC scenario. I
run on a remote Linux server with "-headless". VNC is not started in the
image. If I suspect a problem, then I use the Seaside app at /tools/vnc
to start the VNC server. Then I attach to the image with a VNC client,
and proceed to debug.
I suspect this scenario will be broken. The problem is that the
"-headless" flag does not mean there is no interactive UI needed. It
means that there is no local display. If there is a way the flip the
switch, in the running image, then the /tools/vnc code could flip that
switch.
--
Yanni
