I *think* magic_browzR is redo attempt 1 at redoing the drawing/frame
drawing/etc code for Chome.
There is quite a large raft of bugs relating to the Chrome window,
sizing, resizing, maximizing, minimizing, tiling, cascading, etc.
These include:
1. Resizing when dragging the borders, bottom edge, etc.
2. Being able to drag the 4 borders or not when maximized or not, and
the cursor should change to "resizeable-arrow" or not
3. Window should restart maximized if maxmized before, restart
restored if restored before, etc.
4. Window should obey shortcut properties run normal/maximized/
minimized
5. Window should obey cascde/tile windows horizontally/tile windows
vertically
And if I read the bug comments properly, I think there may be an even
better (attempt 2) new framing code coming soon....
On Dec 1, 5:30 am, "Matthew Lecin" <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 29, 2008 at 15:32, dhhwai <[EMAIL PROTECTED]> wrote:
> >Try adding --magic_browzR to the end of the shortcut target used to start
> >Chrome.
>
> THANK YOU!
>
> That did the trick, it works with RBTray now, as well.
>
> What else *does* --magic_browzR do, aside from getting Chrome to obey
> windows directives such as minimize to tray?
>
> {Mijjil}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
