🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:435049b2$1@newsgroups.borland.com...
>
> "Stefano Bonifazi" <stefboombastic@libero.it> wrote in message
> news:43502184@newsgroups.borland.com...
>
>> But I found that I can set the class of the window they use as floating
>> window when undocked by the "FloatingDockSiteClass" property.
>
> I have never seen that property before.  I'll have to look at that, it 
> might
> help me with some issues in my own projects ;-)

Yes maybe it's a new property of BCB6 ... I don't remember it with BCB5 ... 
And I found other nice properties connected to Docking stuff that I never 
heard about before ... maybe they renewed "Docking" !?!
 >
>> So now I implemented a descendant of  TCustomDockForm to
>> use with them, that does not show the "biSystemMenu" at all :-)
>
> That will not prevent a window from being closed at all.  A user can still
> use ALT-F4 to close an active window even when it does not have a X button
> or a system menu.  Since you are deriving a new class, you can override 
> the
> CloseQuery() method, or override the WndProc() method to intercept the
> WM_SYSCOMMAND or WM_CLOSE message.

Yes and I've already overridden CloseQuery ... but then I found that 
TCustomDockForm::Close acts "like" setting Visible=false of the undocked 
control ... and in my application it's more usefull letting the user to 
"hide" the floating window by pushing the "x" and then make it again visible 
programmately whenever needed :-)

>
>
> Gambit
>
Who other so great ? :) ... Thank You very much Mr. Gambit
Stefano B.