I just have a comment about using the Enigma Protector program's GUI. I often drag my programs around by their titlebar,
and that's fine. However, sometimes I miss the titlebar and click somewhere else. I also tend to click on the dialog (anywhere) occasionally to bring it into the foreground.
I see that if you click outside a checkbox section, the checkbox still gets checked. This is causing me major headaches,
as I don't realize these checkboxes are being checked, and it messes up my project.
Normal MFC programs do not behave this way. They only allow checkboxes to be checked if the mouse is clicked
inside the checkbox. If there's anyway to fix this very irritating GUI behavior, then that would be great.
Enigma Protector GUI suggestion
-
samsonite131
- Posts: 30
- Joined: Tue Oct 15, 2013 10:35 pm
Re: Enigma Protector GUI suggestion
Another suggestion that stems from the last.
Whenever I create a new project, protect a program, and distribute it to users, it's very important to me
that the generated registration keys stay valid at all times. Even if I go back and change some project options.
When testing the Enigma demo, I have found many checkbox options that can break either the regkey or
the regkey API. And a user can do it without any warning. This is somewhat dangerous for a beginner
who is not familiar with the Enigma program. For example, changing the hardwark lock options invalidates
all previous keys, and enabling a "UNICODE" registration scheme breaks the regkey API, causing
functions to fail. In fact, most or all of the options under "Registration Features" are dangerous to touch
after a protected program and keys has been distributed.
My suggestion is just that if there was a way to protect these options, or maybe give a warning message
before changing them, it may help new users like myself from breaking their project. Maybe the entire
"Registration Features" section could be protected from accidental change.
Whenever I create a new project, protect a program, and distribute it to users, it's very important to me
that the generated registration keys stay valid at all times. Even if I go back and change some project options.
When testing the Enigma demo, I have found many checkbox options that can break either the regkey or
the regkey API. And a user can do it without any warning. This is somewhat dangerous for a beginner
who is not familiar with the Enigma program. For example, changing the hardwark lock options invalidates
all previous keys, and enabling a "UNICODE" registration scheme breaks the regkey API, causing
functions to fail. In fact, most or all of the options under "Registration Features" are dangerous to touch
after a protected program and keys has been distributed.
My suggestion is just that if there was a way to protect these options, or maybe give a warning message
before changing them, it may help new users like myself from breaking their project. Maybe the entire
"Registration Features" section could be protected from accidental change.