search

07sdss12 / pixus

Automatically exported from code.google.com/p/pixus
1 stars 0 forks source link

Application stage #37

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Instead of launching Pixus from the default stage/canvas, you should spawn
it in a new native window so it has no boundaries.  This will also
eliminate the need for you to maximize the stage the size of the screen,
thus lowering memory consumption and keeping the application stable over
time.  It will also eliminate the workaround you implemented for multiple
monitors.  You can always open with a splash type screen, then hide it a
spawn Pixus in a new window.

Original issue reported on code.google.com by dzedw...@gmail.com on 5 May 2009 at 9:45

GoogleCodeExporter commented 9 years ago 
In Mac OS X, a NativeWindow can never go above the system menu. With my title 
bar and
skins, the real ruler can never reach things on the top of the Mac desktop. 
That's
why I turned to a maximized window later and designed this multi-screen dragging
feature. 

A few samples.

Dwarf, the same way as mine.
http://www.destroytoday.com/projects/dwarf/news

PixelPerfect, normal window, way too simple.
http://www.adobe.com/devnet/air/flash/samples.html

Hope I find the cure or Adobe AIR will handle it in the future.

Original comment by jammind on 11 May 2009 at 5:08