Since RunUserInterface is, in general, just processing GUI events? The callbacks that handle those events are synchronous calls from the RunUI thread...right? What I'm getting at is...when designing callbacks, it seems best to make them somewhat like an interrupt...short, sweet, and possibly just a means of sending a message to some other worker thread to do the rest of the stuff. Am I on the right track?
Something else of interest here is GUI updating. My GUI is updating inputs by a timer polling on my DIO card. I would like my GUI to have a finer resolution...not so choppy (my system has other processing demands). So, my thought is to make my timer function as short at possible and have other threads do the work (if necessary). However, does anyone know of anyway to setup my DIO signals as software interrupts? Can anyone throw me a bone on optimization techinques for this? Thanks,
