jqt is a single threaded application, ie it has only the main thread (UI thread). J engine also runs on the main thread so that it can block UI events such as paint.
You will also notice there is not session output if running a tight loop. A workaround is to run wd'msgs' at some interval to let pending UI events has a chance to be processed. On Wed, Nov 6, 2019, 2:35 AM Raul Miller <[email protected]> wrote: > Engine: j901/j64avx2/darwin > Beta-m: commercial/2019-10-02T11:28:59 > Library: 9.01.11 > Qt IDE: 1.8.4/5.12.5 > Platform: Darwin 64 > Installer: J901 install > > When I come back to a long running JQt session the editor has... > transparency. > > Some lines of text in the editor will be visible, but the rest shows > content from other windows. > > I can scroll the window to make the content reappear (once I recognize > what's going on - before that, I don't know if it's J that's messing > up or something else), and -- since it's a long running process -- I'm > often not focussing on J at the time. > > Anyways, this smells like the Qt infrastructure having a timing issue > where it can lose refresh events. But, as a workaround, I would like > to propose that if there's more than 24 hours between paint events (or > maybe something more aggressive, like an hour?) that J try to do a > complete paint when that happens (assuming that's possible... I don't > know enough about Qt internals and I *am* guessing, here.) > > Thanks, > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
