Hi; using Python 2.7.5, wxPython 2.9.4.0 cocoa on OSX 10.8.4, custom drag and drop appears broken. I’m upgrading from a rather old version and at first assumed that it was just something that changed or that I was doing wrong before – but!
I decided to go to the demo and run the CustomDragAndDrop and see what I missed… and – the demo isn’t working either 
So, I no longer need to go make up a runnable example. Its broken in the demo on my machine, too!
Basically, DoDragDrop seems to always return 1 / DragNone.
Is this a known bug in wxPython, or something wrong on my system that’s strange or new, oor? Hopefully, is there some workaround someone has found to hack at it to get it to work?
Its worth noting the regular DragAndDrop doesn’t seem to work at all either.
–Stephen
Hi; using Python 2.7.5, wxPython 2.9.4.0 cocoa on OSX 10.8.4, custom drag
same but OS-X 10.7
I decided to go to the demo and run the CustomDragAndDrop and see what I
missed.... and -- the demo isn't working either 
So, I no longer need to
go make up a runnable example. Its broken in the demo on my machine, too!
On nine, if I DnD between the Windows, it doesn't work, but DnD onto
Preview does work -- so only semi-broken. But clearly broken for you
use.
Sorry I don't have any suggestions for a fix, but at least you know
it's not just you.
-Chris
···
On Thu, Aug 15, 2013 at 10:31 AM, Stephen Hansen <apt.shansen@gmail.com> wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
See here:
http://trac.wxwidgets.org/ticket/13874
and related. I’m not sure at a glance whether your problem (mine too!) is fixed or not, but I’m really hoping 2.9.5 is functional…
-Nat
···
On Thu, Aug 15, 2013 at 10:31 AM, Stephen Hansen apt.shansen@gmail.com wrote:
On Monday, August 12, 2013 6:44:59 PM UTC-7, Stephen Hansen wrote:
Hi; using Python 2.7.5, wxPython 2.9.4.0 cocoa on OSX 10.8.4, custom drag and drop appears broken. I’m upgrading from a rather old version and at first assumed that it was just something that changed or that I was doing wrong before – but!
I decided to go to the demo and run the CustomDragAndDrop and see what I missed… and – the demo isn’t working either So, I no longer need to go make up a runnable example. Its broken in the demo on my machine, too!
Basically, DoDragDrop seems to always return 1 / DragNone.
Is this a known bug in wxPython, or something wrong on my system that’s strange or new, oor? Hopefully, is there some workaround someone has found to hack at it to get it to work?
On nine, if I DnD between the Windows, it doesn’t work, but DnD onto
Preview does work – so only semi-broken. But clearly broken for you
use.
My actual use is D&D from grid control to grid control in another window, but even same-window dragging in the demo is broken as far as I can see. Either way, thanks for the confirmation.
···
On Thursday, August 15, 2013 5:07:09 PM UTC-7, Chris Barker - NOAA Federal wrote:
On Thursday, August 15, 2013 5:11:01 PM UTC-7, Nat Echols wrote:
See here:
http://trac.wxwidgets.org/ticket/13874
and related. I’m not sure at a glance whether your problem (mine too!) is fixed or not, but I’m really hoping 2.9.5 is functional…
Gah. I thought there had to be something weird/distinct on my setup, not that wxPython had been so fundamentally broken for so many months. I know the 2.9 is the development line, but I expect more API instability then basic things like D&D simply not working. 
Well, I’ll try out the Carbon build just to see, and failing that, go back to the latest 2.8. I was really looking forward to some 2.9 enhancements.
Thanks for the info.
–Stephen
It was actually working fine in 2.9.2 - unfortunately a bunch of other
stuff wasn't, if I recall correctly. I don't have a choice about Cocoa
support because I desperately need the 64-bit builds, so I've been getting
complaints from users for the last year or so. The port generally appears
to be working okay aside from this, although some of the wxWidgets
maintainers have a habit of removing key features simply because they don't
adhere to Apple's design guidelines. (Fortunately, they've reverted at
least one of these changes under pressure, but the fix also requires 2.9.5.)
-Nat
···
On Fri, Aug 16, 2013 at 11:38 AM, Stephen Hansen <apt.shansen@gmail.com>wrote:
Gah. I thought there had to be something weird/distinct on my setup, not
that wxPython had been so fundamentally broken for so many months. I know
the 2.9 is the development line, but I expect more API instability then
basic things like D&D simply not working.
Well, I'll try out the Carbon build just to see, and failing that, go back
to the latest 2.8. I was *really* looking forward to some 2.9 enhancements.