Hi! On Fri, 16 Jun 2017 11:57:13 +0200 meik michalke <meik.micha...@uni-duesseldorf.de> wrote: > Am Sonntag, 4. Juni 2017, 16:47:37 CEST schrieb meik michalke:
Huh? Did not see that one. Also not in the list archive. > > it seems there has something changed in how RKWard opens RData > > files. it still loads it, but at the same time closes all tabs in > > the main window part. > > > > here's how to reproduce it: > > > > - open RKWard (KF5) > > - open any script file > > - klick on a *.rda or *.RData file That's actually intentional, and I don't think it's new in KF5 (did not bother to check, though). The idea is that a workspace is more like a project, including all related files, and if you close it, the corresponding files are closed, too. Clearly, this isn't desirable _all_ the time, but simply keeping all current windows open is not universally a good idea, either, and can even become confusing in some cases (suppose you have two different projects, containg R scripts by the same name, but different contents. Perhaps something like "preparedata.R"; I believe we even had a bug report about this one day). The _exception_ is that if a workspace is opened via DBus (i.e. from file browser, with --reuse), it does _not_ replace the current workspace. Mitigation ideas? > adding to this, not sure if it's a real bug or inevitable: when > RKWard starts up, the file browser is not set to the working > directory as long as the R backend isn't ready. if you open it too > fast, it shows $HOME, not what is configured. can RKWard set the > configured directory independently from the R backend? I've changed this so the frontend will actively cd to the same dir on startup. Of course WD changes (also for instance, if configured to change directory to current script file) will _not_ be totally synchronous at any rate. However, usually the backend is going to be idle, and so no delay will be noticeable. Regards Thomas
pgpoen6AEcL4e.pgp
Description: OpenPGP digital signature
