I had a realization while drifting off to sleep-- I was in just the
right mindset-- I'm 90% sure I killed my killer bug!!! it accounts for
the problems I've had.
once I realized what it was; it took me 30 seconds to write code to fix
it.
the code isn't neat; but I can do that later.
YEAH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
fixing this bug is CRUCIAL for the code I'm writing to work.
(the code that I need to deliver this week, that my job is essentially depending on)
this is *VERY GOOD NEWS*
I can now go to sleep relieved that this bug that's been haunting me for the last few weeks is now slain.
I could write up an enthusiastic report to detail the bug; but only a subset of friends care...
although I do need to write it up for the code documentation.
essentially:
I'm building a UI to manipulate objects; one task is do drag and drop between two trees; essentially two file trees (ie: two explorer windows)
a
while code to do this exists almost completely, it doesn't do exactly what we want; plus you need to use the newest versions of gwt (google windows toolkit) to use the new libraries, so I can't use them and have to roll a lot of my own stuff. it's certainly a learning experience.
( gwt backgroundCollapse )when moving items from box a to box b; they were being copied to box c as a "preview" of the move -> for a drag and drop operation.
then, when the drag-n-drop ended, the items got moved from a to b.
the problem was; when the items were getting copied from a-->c; the items in box a were getting marked for deletion right then; and if the move was canceled, then :
1) items got deleted from box a
2) items never got moved to box b
--> so the items essentially disappeared.
whenever I did an accounting, all items were present, just some were marked for deletion that shouldn't have been (nothing in box a actually got removed, they just got marked for deletion and then not drawn).
this is SUCH a relief.