|
2006-07-22 14:21
|
Event_Editor_Bug.jpg (21,453 bytes) |
|
|
Do you know when this was introduced? |
|
|
No I am a new FRED user. (And I'm running on a 56Kb Internet connection because my ADSL is out. So I won't be able to download CVS versions to pinpoint it for a while). |
|
|
This has been around since retail. It's just one of FRED's many idiosyncracies. |
|
|
I am assigning this as a future feature. |
|
|
ignore as this will probably be fixed by wxFRED (is that even still being worked on?) |
|
|
Ok, found the reason for this, but I'm not quite sure why it's there in the first place so I don't want to remove it without someone agreeing with me. In sexp_tree.cpp, the right_clicked() function, there is a SelectDropItem() call. There is no call to let go of said item however, which is why it can't move on to something else. Now, I don't know MFC worth a crap, but looking over the code I can't find a single reason for that call to be there. Simply commenting that line out makes the tree work as expected (though I didn't really give it that good of a test). Anyone know if it's safe to get rid of that call in order to fix this bug? (SelectDropItem() is the call to do mouse drag-and-drop. Drag-and-drop is already handled by specific functions for that purpose however and this call in particular doesn't appear to have affiliation with the actual drap-and-drop functionality.) |
|
|
Perhaps :V: meant to allow users to drag events around? I say just remove it. |
|
|
Yeah, but you can't drap-and-drop while the context menu is there anyway. Events (parents, not the individual sexps) are already drag-and-drop, though this right-click issue might interfere with that working properly. I'll just go ahead and remove it and we'll see if anyone has problems. |
|
|
Fixered. |
- Anonymous
