-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
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. |
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. |
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. |
I’m happy with an .ini file solution. If we try it out and feel we really want it in a menu, we can ask for that, but for now, this gives us a chance to experience this option and see if we really wanted it or not.
Thanks!
…-Beth
On Mar 19, 2023, at 10:59 PM, cdfarrow ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA62JLG4EUJX5CKVTLWKZDLW47I25ANCNFSM57GZCVOA>.
You are receiving this because you commented.
|
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.
The text was updated successfully, but these errors were encountered: