> > I don't think that's a good idea. This just leads to the "Blackbox > calls themes styles" behaviour: something that is called 'foo' in > virtually all window managers has a certain behaviour. Only in > blackbox, the thing that's called 'foo' does something else, and for the > user to see the behaviour, she needs to use 'bar'. > > Shading is shading is shading and should not be treated as iconifying > (even if it's recommended as an iconify-substitute, as BB doesn't have > any "real" iconify, just "hide" or "vanish"). > > Just IMHO and my $.02 > -Jan
Actually, according to the specs shaded windows are to be marked in the "icon" state. In fact blackbox has always done this. So this seems to be the next logical step. Now, to reiterate all I am suggesting is that when a new window is launched it ignores shaded windows. So if you have a large web browser open and shaded in the middle of the screen you can still launch a window with out it hitting the cascade placement code (which is the old behaviour). So without this patch what happens in the above scenario is window #2 is opened at (32,32) plus any nudge for the toolbar or slit. Window #3 would be at 32 + titlebar height, 32 + titlebar height and each window after would load up titlebar height further cascaded. With the patch normal window placement occurs.
