RE: [gtkmm] What is the best way to diagnose a non-drop

["Ohrnberger, Erik" <erik_ohrnberger dme net>]

Aaarch!  Stoopid me!

Well, as it turns out, gcm really didn't help all that much for drag and
drop operations.  However, I did find the problem.

In the target widget, in the drag_dest_set method call didn't have the
Gtk::DEST_DEFAULT_ALL and Gdk::DragAction( GDK_ACTION_MOVE ) arguments, so
it's no wonder that it would not accept a drop action.  Once I got this
fixed, it accepted the drop action.  Arg.  Stoopid me.

	Thanks for your help,

		Erik.

> -----Original Message-----
> From: Murray Cumming Comneon com [mailto:Murray Cumming Comneon com]
> Sent: Wednesday, November 19, 2003 3:33 AM
> To: erik_ohrnberger dme net; gtkmm-list gnome org
> Subject: RE: [gtkmm] What is the best way to diagnose a non-drop
> 
> 
> Ohrnberger, Erik wrote:
> > 	I was just wondering if there was a good method to 
> > diagnosing why something which you think should be a drag and 
> > drop target is not allowing the drag and drop source to drop there.
> > 
> > 	I'm thinking of some calls where the drag and drop 
> > source & targets are compared just to check them.  Any 
> > recommendations?
> 
> This clipboard manager might be informative, or it might 
> confuse you even
> more:
> http://gcm.sourceforge.net/
> 
> Please tell us if you resolve the problem, so people find it 
> in the archive.
> 
> Murray Cumming
> www.murrayc.com
> murrayc usa net
>