Chris Barker wrote:
Torsten Sadowski wrote:
when using closely spaced buttons under OSX I noticed, that on MouseDown
a larger area than the button area is repainted which damages adjacent
controls. Either the redraw area or the size used by the layout tools
(sizers and layoutconstraints) has to be changed. This is only cosmetic
but ugly.This is a known bug. I thought Stefan had done a simple fix of padding
the buttons with some extra space, so that sizers wouldn't put them so
close together.
I think he abandonded the idea because it caused more problems than it fixed. Something has been done in the 2.5 tree to help but I think you still have to have space between your widgets.
This wouldn't allow you to put them as close as you'd
like, but I think that is a Carbon problem, not a wxWindows problem.
Actually Carbon is just the APIs andand framework and such, it is Aqua that isproviding and drawing the widgets. IIRC the same Aqua code is used from both Carbon and Cocoa. (Or I could just be out in left field as I still trip over all these names sometimes.)
Luiz Siqueira Neto wrote:
Why we don't port wxPython to Cocoa, Carbon is a transition technology and
really don't offer a good experience to user.
It has been started already. See the thread starting at http://lists.wxwindows.org/cgi-bin/ezmlm-cgi?5:mss:35876:cfhcginkdpoaamcliheh
A number of reasons:
1) wxWindows is C++...can you use Cocoa from C++ ?
No, but you can from Objective-C++ and C++ can call to Objective-C++.
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!