Opened 5 years ago

Closed 10 months ago

#15059 closed enhancement (outdated)

Grid segfaults upon destruction when multiple pieces are drop targets

Reported by: mears Owned by:
Priority: low Milestone:
Component: wxPython Version: 2.9.4
Keywords: Cc:
Blocked By: Blocking:
Patch: no

Description

Attached is GridDragAndDrop.py from the demo with one change.

In addition to: self.SetDropTarget(dropTarget)
I've added: self.GetGridRowLabelWindow().SetDropTarget(dropTarget)

This enables users to drag items on top of row labels. Simply run the example, and close it. It will segfault. Note, that you can use either one of those statements in isolation. It's only when they are used simultaneously that there is a problem.

Attachments (1)

GridDragAndDrop.py download (2.7 KB) - added by mears 5 years ago.

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by mears

comment:1 Changed 5 years ago by mears

  • Priority changed from high to low
  • Type changed from defect to enhancement

Of course, discovered the source of the problem immediately after creating this ticket. It wasn't apparent to me that drop target instances cannot be shared. A quick Google shows I'm not the first to run into this. Would it be worthwhile to add a note to the documentation for SetDropTarget indicating this?

comment:2 Changed 10 months ago by robind

  • Resolution set to outdated
  • Status changed from new to closed

Closing old Phoenix tickets...

If this is still an issue in wxPython 4.0.0a1 then please open a new issue (or PR) at the wxPython-Phoenix project page on Github: https://github.com/wxWidgets/Phoenix

Note: See TracTickets for help on using tickets.