Francois,
> Paul, you told me in your intial message that having a handle still
> allocated prevent desktop switching. As I know you are using threads, I
> just
> wanted to remind you that to destroy a window handle, you must call
Not quite:
I wrote "Are there any handles left after freeing the
>>> Everything is created in the threads execute, so that should be fine.
>>
>> You have to destroy also at the end of the execute method or from a
>> function
>> called from there.
>
> Sure, but that is not the problem.
> When a desktop change is detected, these steps are executed:
> - destroy Htt
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
>> Everything is created in the threads execute, so that should be fine.
>
> You have to destroy also at the end of the execute method or from a
> function
> called from there.
Sure, but that is not the problem.
When a des
>> Should be no handle left. But pay attention that if you destroy any
>> control
>> with a window handle from a thread which has not created the control,
>> then
>> the window handle is /not/destroyed (DestroyWindow fails but usually his
>> return value is not checked).
>>
>
> Everything is creat
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Friday, January 26, 2007 9:04 PM
Subject: Re: [twsocket] Handles in components
>
> Should be no handle left. But pay attention that if you destroy any
> I'm having troubles with switching between desktops using the (Ssl)HttpCli
> in a thread with message pump.
> You can't switch between desktops when handles are used.
> So I'm trying to switch between desktops by freeing the client, switch to
> new desktop and recreate the client, but this thread
I'm having troubles with switching between desktops using the (Ssl)HttpCli
in a thread with message pump.
You can't switch between desktops when handles are used.
So I'm trying to switch between desktops by freeing the client, switch to
new desktop and recreate the client, but this thread fails t
