Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow double-click of modules that modify #18

Closed
rmlockwood opened this issue Aug 22, 2022 · 4 comments
Closed

Allow double-click of modules that modify #18

rmlockwood opened this issue Aug 22, 2022 · 4 comments

Comments

@rmlockwood
Copy link

Right now, if you double-click a module that is set to modify the database, you get an error to use RunModify. Couldn't FLExTools know that it's a modify module and bring up the 'Are you sure' messagebox at that point rather than an error? I've done this countless times and I have a user who asked for this kind of fix to be made.

@bbryson
Copy link

bbryson commented Aug 24, 2022

I agree.

I also wish there were an option to tell it not to ask me "Are you sure?" every time. Or is that ill-advised? Maybe make it as an "easter egg"? That is, we have to know the magic incantation.

@cdfarrow
Copy link
Owner

cdfarrow commented Sep 6, 2022

The reason it behaves like this is because of the "Dry run"/"Do it for real" model of operation. The default operations (double-click, enter, and the standard Run buttons) are activating the dry run mode. It is like a safety switch, and the error message is to prompt the user to release the safety guard by using the Shift key or use the Modify buttons. See #19 for a suggested improvement that addresses this.

@cdfarrow
Copy link
Owner

cdfarrow commented Mar 20, 2023

I also wish there were an option to tell it not to ask me "Are you sure?" every time. Or is that ill-advised? Maybe make it as an "easter egg"? That is, we have to know the magic incantation.

You can now specify "warnonmodify = False" in the ini file to do this. I might make it a toggle in a menu at some point.

@bbryson
Copy link

bbryson commented Mar 20, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants