taoujouti / macwidgets

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

Custom Drag Code for Unified Toolbar does not recognize spaces change. #48

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The java unified toolbar has custom drag code to change window position.
This works, as long as the user does not want to change the space the
window is into. (dragging, holding the mouse, pressing strg-2 for example)

it works if the window is hold on top (native moving code on titlebar)

so i experimented with apple.awt.draggableWindowBackground.
no luck so far...

anyone already tried that client property? (java6u7, mac10.5.6)

there should be both the java moving code and the client property, so that
this works cross platform...

Original issue reported on code.google.com by studp...@gmail.com on 12 Jan 2009 at 1:01

GoogleCodeExporter commented 9 years ago
Well, seems this is already known and there is no good workaround... too bad.

http://explodingpixels.wordpress.com/2008/05/03/sexy-swing-app-the-unified-toolb
ar-now-fully-draggable/

Original comment by studp...@gmail.com on 12 Jan 2009 at 1:05

GoogleCodeExporter commented 9 years ago
BTW: Can you install the drag handler on the statusbar? iTunes is draggable 
that way.
(Or I added the statusbar in a weird way)

Original comment by studp...@gmail.com on 12 Jan 2009 at 1:07

GoogleCodeExporter commented 9 years ago
I believe the spaces issue is a none Java-on-the-Mac issue, so I'm inclined to 
close this issue.

As for the making the BottomBar draggable, you can do it like this:

bottomBar.installWindowDraggerOnWindow(frame);

See the DBottomBar demo for details.

Original comment by kenneth....@gmail.com on 13 Jan 2009 at 12:30

GoogleCodeExporter commented 9 years ago

Original comment by kenneth....@gmail.com on 16 Jan 2009 at 11:59

GoogleCodeExporter commented 9 years ago

Original comment by kenneth....@gmail.com on 16 Jan 2009 at 12:00

GoogleCodeExporter commented 9 years ago
This is an Apple bug, thus I'm closing this issue.

Original comment by kenneth....@gmail.com on 30 Jan 2009 at 12:11