Hi all, I use RSHOW from a RMD file in my main app to QUIT to the R:> and it “seems” to be behaving differently from usual recently.
The RMD files set various things up for me and then is supposed to show the R:> screen before WRITing various bits of information – version number, current directory, that sort of thing. I have only the “Show R>Prompt” option checked in the Startup Options in the Settings menu. What seems to be happening is that the main R:Base window appears with just a grey screen, ie nothing open, not the R:> or anything else. The RMD file completes and then the R:> screen appears but nothing is shown as there was no R:> screen to print to. The RMD file uses QUIT as it’s last command and that’s when the R:> screen appears (without the expected text shown). I’ve experimented with various repeats of RSHOW, PAUSEs and added a RETURN after the QUIT but nothing seems to work. If I open R:Base and run the RMD file from an already open R:> screen everything works as it should. I’m tempted to say it’s changed since the last update but I’m not sure as I hadn’t been doing much work at the R:> for a while until recently. Has anybody noticed this or any ideas what might be causing it? As an aside, might it be nice to have an RSHOW command with an option to show whichever module is required (Explorer/R:>/Editor)? Regards, Alastair.
