[werner] Problem making child window at startup - SOLVED

Lars Werner lars "at" werner.no
Mon Jan 26 06:21:01 2004


Hi

Problem solved :P

I just had to make the window before the run_undetached calls
realisefullscreen, then the message queue for the window will end up in the
right wndproc :)

If anybody else have any problems with this, please create a childwindow
after createwindow in clientconnect.cpp file (ln 271)

Regards
Lars Werner
http://lars.werner.no

----- Original Message ----- 
From: "Lars Werner" <lars "at" werner.no>
To: <vnc-list "at" realvnc.com>
Sent: Monday, January 26, 2004 12:20 AM
Subject: [werner] Problem making child window at startup


> Hi there...
>
> I'm currently making a toolbarwindow for RealVNC inn fullscreenmode, and
I've
> runned into some problems. I've integrated my window into RealVNC and it
works
> great with one exception
>
> If the check "FullScreen" is checked before connection, the
> "RealiseFullScreen();" is called in the run_undetached procedure.
>
> In the ClientConnectionFullScreen I've made a child window that is created
> based on the m_hwnd variable, and it makes the VNC go into infinity loop
when
> it is done at startup. Has anybody encountered that before? :P
>
> If the same routine is used later after I've got a picture from the remote
> machine, then everything is working normal. I've also tried to make the
"child
> window" without any parent, and it will not show at startup, but later in
> runtime everything is ok.
>
> I'd love to get some help fixing this problem,
> best regards
> Lars Werner
> http://lars.werner.no
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list