On Thu, 2006-09-07 at 20:26 -0400, Erik Blankinship wrote: > On 9/7/06, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > > Erik Blankinship wrote: > > > Right now, when toggling the taskframe on/off (F5), activities' edges > > > are covered up. > > > > > > Is this the default behavior, or should we write our apps to > > > dynamically resize to the new available screen real estate? > > > > No, that is the intended behavior. Activities should just take the whole > > screen. > > > > > Will the > > > taskframe's dis/appearance be animated at some point? > > > > Yes, it will. I hope to have more informations about the visual design soon. > > > > > Regardless, what event do we listen for to know when the taskframe's > > > appearance is toggled? > > > > What is the use case for this? > > I would like to know which activity pixels are displayed and which are not.
Because...? > Appearance of the taskframe might also impact intercepting > mouse-events, or, dragging to/from the taskframe. That's kind of the point... the frame has to intercept mouse events to be able to do what it does. Dan > _______________________________________________ > Sugar mailing list > [email protected] > http://mailman.laptop.org/mailman/listinfo/sugar _______________________________________________ Sugar mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/sugar
