wxruby development - Aug 2008 - [ wxruby-Bugs-21491 ] Wx::STAY_ON_TOP and Wx::NO_BORDER messes with Sizer layouts.

Bugs item #21491, was opened at 2008-08-08 11:00
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=21491&group_id=35

Category: Incorrect behavior
Group: current
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Wx::STAY_ON_TOP and Wx::NO_BORDER messes with Sizer layouts.

Initial Comment:
I am making a full-screen app that I want to stay on top (to re-create something
similiar to this app: http://hogbaysoftware.com/products/writeroom for a
multi-platform use.) however, I am running into a strange issue.

If I use this:

def on_init
  x = Wx::SystemSettings.get_metric(Wx::SYS_SCREEN_X)
  y = Wx::SystemSettings.get_metric(Wx::SYS_SCREEN_Y)
    
  @frame = Wx::Frame.new(nil, -1, APP_NAME, [0, 0], [x, y], Wx::NO_BORDER)
  ...

...my on-screen buttons are not spaced out in the sizer, but instead are one on
top of the other.  Any combination that contains either STAY_ON_TOP or NO_BORDER
does this.  Removing them, the sizers layout their contents correctly.

I''ve moved to using TopLevelWindow::show_full_screen to force the
max-size, but part of the app''s purpose it to cover the entire desktop,
not have a border, etc...  Any idea why the control overlapping/sizer issue is
happening?

This is one Windows Vista, for what it''s worth, ruby 1.8.6, and
whatever wx-ruby that came with the install.  Have not had a chance to check on
my linux box yet.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=21491&group_id=35