[1]
>
> wxBitmapButton:
> - If you during runtime change the bitmap on the button it will not
> show the new bitmap until you do a manual refresh call.
This is normal, Windows will sometimes behave the same way.
>
> wxButton:
> - The wxButton.SetForegroundColour does not work at all, and the
> wxButton.SetBackgroundColour does not set the background colour
> of
> the button but on the background behind the button (ugly!).
This is expected due to the way that the native button draws itself, and
is also why wxWidgets is not able to guarantee that any visual attribute
change on any native widget will be successful.
>
> wxComboBox:
> - Appending choices to a combobox after initialization does not
> work,
> i.e. the new choice does not show up
[1]
>
> wxFrame:
> - Calling wxFrame.CentreOnScreen() when the frame size is set to
> very
> big will cause the frame system menu to be hidden underneath the
> mac menu.
Yep, known problem.
>
> wxMenu:
> - EVT_MENU event IsChecked method always returns 1.
[1]
>
> wxNotebook:
> - After adding a page to the notebook and selecting it you again
> have
> to manually call wxNotebook.Refresh to see the new panel inside
> the
> notebook.
[1]
> - If you add more pages than the size of the notebook allowes you
> will
> not get scroll buttons (like you do on eg. wxGTK) but the pages
> are
> just drawn on the side of the notebook and you can't select them.
Yep, this is a known issue and is due to limitations in the native
widget. Apple apparently feels that a notebook should never have more
than a few tabs. You should use one of the generic alternatives
instead, such as FlatNotebook.
> - The wxNB_LEFT, wxNB_RIGHT or the wxNB_BOTTOM styles do not work.
Ditto
> - Adding a new page to the notebook with
> wxNotebook.AddPage(p, l, selection) and selection is set 1 does
> not
>
> select the new page . Note! When calling
> wxNotebook.SetSelection()
> afterwards still keeps the focus on the old page but the new
> selected page is shown.
[1]
>
> wxNamedColour:
> - Is probably not implemented?!
That is generic code and so should be present in all builds. Did you
spell it correctly? What error are you getting? [1]
>
> wxSpinCtrl:
> - Calling wxSpinCtrl.Show(true) will disable the widget, even
> calling a wxSpinCtrl.Enable(true) afterwards does not help!
[1]
>
> wxTimer:
> - A wxTimer.IsRunning() call does not give you the correct result
> if your timer interval is short i.e. the system load is high.
That is to be expected on any platform.
>
>
> and also I can see each cursor in each stc in scrolledpanel on MAC.
I'm not sure I understand what you mean with this one. Are you saying
that the caret is still visible and flashing in the STCs that do not
have the focus?
[1] For each of these items please make a small runnable sample that
demonstrates the problem (and nothing else.) If you don't find that you
have made a mistake in how you are using the widget then send the sample
here. Also be sure to let us know which version of OSX you are using
and the version of wxPython and whether you are using the Carbon or
Cocoa build.
--
Robin Dunn
Software Craftsman
http://wxPython.org
- If you add more pages than the size of the notebook allowes you
Yep, this is a known issue and is due to limitations in the native widget. Apple apparently feels that a notebook should never have more than a few tabs. You should use one of the generic alternatives instead, such as FlatNotebook.will
not get scroll buttons (like you do on eg. wxGTK) but the pages
are
just drawn on the side of the notebook and you can't select them.
I wholeheartedly agree on this one. I normally am a great admirer of
Apple widgets and tools, but I am sorry to say that they got the
Notebook stuff completely wrong. Not to mention the tabs appearance,
which is sub-par compared to other great-looking Mac widgets.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
They got rid of the neon blue buttons, notebook tabs and etc. in 10.7 so
things like that look better now. Still not super great, but definitely
better.
--
To unsubscribe, send email to wxPython-user...@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en
Because the SpinButton on Mac doesn't continue to send UP/DOWN events
when the internal counter has reached its min/max values like it
apparently does on the other platforms. After a quick glance at the
docs I'd say that the official behavior in this case is undefined.
You can work around this by calling the spin button's SetRange method
with a very large negative and positive value