From: <bra...@om...> - 2005-04-27 02:02:47
|
Alex Tweedly wrote on 04/26/2005 07:39:39 PM: > I was able to get the resizing to misbehave readily, but have had > less success finding failures in the move operation (with mouse - > not talking about arrow keys here). > Do you have any other "recipes" for getting the move component > failures to happen ? > Do you see them on all platforms ? Yes, I do see moving problems here and there with some widgets. Here is a recipe for the ComboBox bug: ComboBox on Mac OS 10.3.8, wxPython 2.5.5.1, PythonCard from CVS: Open Resource Editor. Create a new ComboBox. Try to move it and you will probably have difficulty. The only way to move it is to grab the edge. Grabbing the middle doesn't work, nor does grabbing the popup menu handle on the right side. ComboBox on Windows XP, wxPython 2.5.3 ansi, PythonCard .81: On Windows the behavior is slightly different for ComboBox. You can grab the right popup menu handle to move the ComboBox (at least you can most of the time), but try grabbing the middle of the ComboBox and you may see some strange behavior. If it doesn't happen right away, keep trying. Alex Tweedly wrote on 04/26/2005 07:39:39 PM: > I can make it misbehave - by double clicking in a component and then > clicking outside it - the component is selected for moving, and > further unrelated mouse events seem to be ignored (solved by giving > focus to another app, then back to this one!) I've also seen another type of resizing problem, only affecting buttons on the Mac. Sometimes a button will not allow itself to be resized vertically, only horizontally. Often, I'll see a button that was created under Windows look very strange on a Mac, because the visual outlines of the button don't match the outlines of the widget (the little square handles are not in the right places). Usually the only way to resize is to edit the resource file manually, though on some occasions I can resize the button in the Resource Editor to fix the problem. |