> In my own Free Pascal widget set, I debated the same issue a few weeks > back. I concluded that the Window State method using 'wsFullScreen' is > the better approach. The reason being - if you look at the > BorderSyle, you can have Dialogs Windows and Tool Windows. They are > pretty much the same thing, just the title bar is different (and > sometimes the border resize feature). In other words Tool Windows are > a special (or specialized) Dialog - as far as I am concerned. Same as > what wsFullScreen is a special (or specialized) wsMaximized.
I tend to agree with Graeme here. As for the keyboard/mouse grabs - shouldn't these perhaps be mapped to TWindow/TForm properties as well ? When we were doing TPopupNotifier we concluded that to be true to common coding standards you should support: TPopupNotifier.Show; But ALSO TPopupNotifier.Visible := true; (And inverse for hiding) By that logic one should be able to do either: TWindow.Grabmouse ; Or TWindow.MouseGrabbed := True; What do you think ? -- "80% Of a hardware engineer's job is application of the uncertainty principle. 80% of a software engineer's job is pretending this isn't so." A.J. Venter Chief Software Architect OpenLab International http://www.getopenlab.com | +27 83 455 99 78 (South Africa) http://www.silentcoder.co.za | +55 118 162 2079 (Brazil)
pgpotYSLZI3jj.pgp
Description: PGP signature
