On 1/22/2014 1:33 PM, Jeremy wrote: > I have a rather complex signal processing GUI that is nearly in its > final state but there are a few bugs I am still chasing around. There is > one strange bug that keeps popping up but it is never reproducible. The > main GUI basically has a few list boxes for different files and channels > and a bunch of other options, and occasionally the content in all the > GUI elements will switch over to set of data that hasn't been loaded for > some time. It really is like some sort of memory lapse, but it seems to > only affect the GUI fields, not the actual data and arrays that are in > the workspace. > > I know this is kind of vague and I can't really post the code, but does > this sound familiar to anyone? It does seem to occur more on some > machines than others.
I don't do GUIs so this is purely supposition -- is it possible there are cached callbacks not previously executed that are finally working their way to the top of the queue?