I have hit a bit of a wall here, i have a bug that is hard to debug because i am finding it difficult to break into the program at a time that will reveal the fault,
I click on an item (so my final event = mousebutton upclick)
then if i leave the mouse dead still over the item i see it toggling fast between the normal 'no-interaction' image and the 'selected'(ie just been upclicked) image
i have tried all kinds of debug breaks and temp counters to try and let me in on the fault occurrence.
stepped through everything a hundred times,
it is difficult because if i break after the initial upclick then step through, everything remains fine, i see the event queue clear down to 1/"001" which i think means no event, as it should, and the image mask to be applied remains the correct one, and i cannot see it go back into the condition 'mouse upclick' (which is definitely what is happening in the bug), it skips it as it should
but if i then set the breakpoint where it would normally flow if a second mouse click had ocurred it steps right into it and gives me the break, which going by my previous stepping through should not happen...grrrrrr!!!
if i just leave the program running as i say, i see it flicking between two conditions.
do you think i should be flushing events or something? the same logic works in another program which is presently being rewritten and i have compared them side by side
bit difficult to post a small snippet for this, i wonder if anybody could think of any known or common mistakes of this sort?