Marcel Kilgus writes: > >> I didn't mean your picture. In QPAC2 Files, unlike the other windows, > >> the title text is a button and therefore can't have the same > >> background as the surrounding title bar. You see the problem pretty > >> well in my original picture. > > It really wants an application window there instead. > > Hmm, good idea. Probably not a 5 Minute job as the button is pretty > dynamic (no fixed size etc), but a possible solution nonetheless. Thx.
Nothing with Wman is a five minute job, unfortunately ;) Wman is great for straight forward, simple things; the moment you want to do something more sophisticated youre into deep waters. You may know all this already, but I'd like to share a few tips on this matter with programmers who may find programming with Wman to be futile rather than a mere PITA. Using an Aplication (sub-)Window in place of a Loose (menu) Item, like I suggested above, gives you a lot more flexibility: You can have different colours, borders, behaviour, and even use a different pointer sprite. (Check out my experimental FastFind utility to see some examples: Move and Resize, the Dirs button, the removable command bar, and the button used for the application when it is "asleep".) However, there are a number of things to look out for: Users of Qpac2 will know that if you press F3 anywhere in Files you get the Command dialogue. This is because that action was defined as a LI in the main window layout. However, keystrokes intended for the main window dont get passed on if the pointer happens to be in an AW. So if you want the same keystrokes to be effective wherever the pointer happens to be, youll have to put pointers to the appropriate action routines in the AWs too. The only way to do this, AFAIK, is to let the AW have dummy LIs for all the relevant keystrokes. A dummy LI is one that has no extent, ie its size is 0x0 and its location could also be 0x0 relative to the AW. The action routine pointer could just be pointers to the existing routines for the main window. This, of course leads to other issues, such as what to do about the status block, but I wont go into that here. In the example in question, these issues must have been resolved, as there already is an AW, namely the file list AW, that allows the same keystrokes as in the main window. Per
