[visit-developers] Any reason NOT to read visitrc file at Commands.../MacrosŠ invokation instead of startup

Miller, Mark C. miller86 at llnl.gov
Tue Jun 2 17:27:06 EDT 2015


Ok, yeah. I am not suggesting we never read visitrc. I am just making an argument to move the time we read it (and start the CLI for it) to something that is more suggestive of the user's need for it in the current session; That is, they dive into Options->Command… or Options->Macros…

Mark


From: Brad Whitlock <bjw at ilight.com<mailto:bjw at ilight.com>>
Reply-To: "visit-developers at elist.ornl.gov<mailto:visit-developers at elist.ornl.gov>" <visit-developers at elist.ornl.gov<mailto:visit-developers at elist.ornl.gov>>
Date: Tuesday, June 2, 2015 1:40 PM
To: "visit-developers at elist.ornl.gov<mailto:visit-developers at elist.ornl.gov>" <visit-developers at elist.ornl.gov<mailto:visit-developers at elist.ornl.gov>>
Subject: Re: [visit-developers] Any reason NOT to read visitrc file at Commands.../MacrosŠ invokation instead of startup

Now that I re-read your message a little more closely, I think you're proposing not starting the CLI unless the Macros window or Macros tab on the Commands window gets shown. If that can be done reliably then I have less of an objection to deferring the CLI.

Brad


On Tue, Jun 2, 2015 at 1:36 PM, Brad Whitlock <bjw at ilight.com<mailto:bjw at ilight.com>> wrote:
Hi Mark,
   When I added "visitrc" to VisIt, it was with the intent that if the file is present then the CLI should be launched automatically. The visitrc file is meant to contain macro functions that get registered with the Macro window to add useful 1-click operations to the GUI. I think LBL's ANAG users make use of the macro stuff to make shortcut operations that would normally require a lot of GUI operations. Again, these things were desired on startup. Gunther could probably comment whether this is still the case.

I saw the redmine ticket and it looks like the user made a mistake. If macros were not desired then why use that tab in the Commands window? Maybe a prompt when settings are saved would be appropriate: "You have added macros which will cause VisIt's command line interface to run on startup. Do you want to save those macros?" Or, maybe have an option to remove macros and the "visitrc" file, if that's not already there. I think those responses would be better than not letting "visitrc" operate as intended.

Brad


On Tue, Jun 2, 2015 at 1:23 PM, Miller, Mark C. <miller86 at llnl.gov<mailto:miller86 at llnl.gov>> wrote:
Hi all, especially Brad,

We'd like to adjust VisIt startup to NOT read visitrc file and put up associated CLI window.

instead, we'd like to move read of visitrc and creation of CLI window to whenever a user happens to dive into Options->Command… or Options->Macros…

This way, users with visitrc files don't get the CLI window until its clear they are likely to want it.

Does anyone see any gotchas here or other reasons NOT to do this?

Mark



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://elist.ornl.gov/pipermail/visit-developers/attachments/20150602/11440620/attachment.html>


More information about the visit-developers mailing list