After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690838 - win32 : cursor for dnd fails
win32 : cursor for dnd fails
Status: RESOLVED DUPLICATE of bug 696756
Product: gtk+
Classification: Platform
Component: Backend: Win32
3.6.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-12-28 21:45 UTC by LE GARREC Vincent
Modified: 2013-08-21 02:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example that show warning's messages (2.17 KB, text/x-c)
2012-12-28 21:45 UTC, LE GARREC Vincent
  Details
Easy hack that solves the problem (741 bytes, patch)
2012-12-28 21:50 UTC, LE GARREC Vincent
none Details | Review
Easy hack (2) (747 bytes, patch)
2012-12-29 08:38 UTC, LE GARREC Vincent
none Details | Review

Description LE GARREC Vincent 2012-12-28 21:45:30 UTC
Created attachment 232353 [details]
Example that show warning's messages

Under Windows, when I try to DnD an item from a GtkTreeView, I have some warnings.
Please, try the enclosing test and tell me if you also have a message when you try to DnD the first line of the TreeView.
Comment 1 LE GARREC Vincent 2012-12-28 21:50:37 UTC
Created attachment 232355 [details] [review]
Easy hack that solves the problem
Comment 2 LE GARREC Vincent 2012-12-29 08:38:34 UTC
Created attachment 232362 [details] [review]
Easy hack (2)

Sorry, first patch is wrong.
Comment 3 Fan, Chun-wei 2013-08-21 02:32:48 UTC
Hi LE GARREC Vincent,

It does seem to me that this roots to another bug that you have reported, bug 696756, as your patch there fixes this issue, together with asserts that are triggered when selecting menu items.

I will close this bug as a duplicate of 696756 now.

With blessings, thank you!

*** This bug has been marked as a duplicate of bug 696756 ***