Just tried it out, and have deprecated my own caching mechanism in its favour.
We'll wonder how we ever did without it. Just one small point: if the window is moved by dragging, or blitted using pmove, the cache (~config/winpos.dat) is not updated. If exit_z_ is then called, the last window position is not cached and on relaunch the window reappears in its old position. This sort of hard exit might well be performed by a single-form standalone app (e.g TABULA) that hides the Qt IDE. One remedy is to replace exit_z_=: 2!:55 with a verb that first calls the destroy methods of all open windows. In the case of qtdemo/pmoves.ijs that happens to be: pmovesdemo_close. I think that's a tidier, more object-oriented strategy than proposing an additional wd-command to clear the winpos cache, or a third variant of pmove/pmoves which not only blits the window but updates the cache. On Mon, May 28, 2018 at 2:01 AM, chris burke <[email protected]> wrote: > The latest Jqt supports wd 'pmoves'. > > Get the latest Jqt binary and demos/qtdemo addon, then see the demo > Help|Studio|Qt Demos|pmoves . > > On Sun, May 13, 2018 at 4:35 PM, Ian Clark <[email protected]> wrote: > > > @Chris -- that sounds just fine! > > > > I had missed the significance of your proposed wd'pmoves'. With winpos in > > my thoughts, I'd pictured an explicit call at init and quit, not a part > of > > the form definition. > > > > I suppose it could also be done as a styles option, as per > > http://code.jsoftware.com/wiki/Guides/Window_Driver/Parent > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
