maximizing the stack/card

[Richard Gaskin]

Alex Tweedly wrote:
>> Most apps that have a single window for a universal toolbar do so in 
>> an MDI, but since we don't have MDI parent window classes there's not 
>> much we can do on that front.  And since MDI is being slowly retired 
>> anyway I'm not sure we'd want to invest in that at this time.
>>
>> With Rev, the toolbar is detached and, perhaps more significantly, 
>> cannot be moved.  So if the windowBoundingRect were not adjusted to 
>> account for it, it would be too easy to have a document window 
>> positioned beneath it so that we can't reach the drag bar.
> 
> Ummm - we're talking about MS Windows,  right ?

D'oh!  Good catch.  I must remember to sleep this week...

> The menu/tool bar isn't fixed position; I can move my toolbar anywhere I 
> want - both on Win-XP and back when I was on Win2000; and also it's not 
> full width, so there wouldn't be any problem reaching the drag bar of a 
> max'ed window beneath it. In fact, earlier on this thread, I mentioned 
> the fact that windowBoundingRect has its top set to be immediately below 
> the toolbar - even if that meant that the windowBoundingRect would be 
> off screen. That I'm sure is a bad idea; I can see the merit in trying 
> to keep the max'ed windows from obscuring the important IDE ones - but 
> they should have done the same with the toolbar as they did with the 
> floating tool palette - reduce the "max" size to avoid it *if* it's in 
> the "expected" place, otherwise ignore it.

Agreed.

But the main point worth noting for the folks here is that none of this 
affects one's own standalone apps.

The implementation of the windowBoundingRect in the engine is pretty 
nice, and as far as I can tell it conforms with expectations.

What Rev decides for their own app doesn't affect any decisions we can 
make with our own.

--
  Richard Gaskin
  Managing Editor, revJournal
  _______________________________________________________
  Rev tips, tutorials and more: http://www.revJournal.com