How I am going to implement (depends on Lupo73's overall decision though) is the Profile Encryption is disabled by default, only when it is enabled by the user will it be available/used. To manually edit the INI files (not recommended!) the program would have to be started for the profiles to be decrypted and then closed to be encrypted. The password will not be available to the user(s).
Again, like everything its a feature request, so it might not be everybody's cup of tea, this is sometimes a problem. Its hard to please everyone as some will see this as useless and others won't, at least it can be disabled though

Quote:
To me, graphics makes interfaces more efficient
Maybe efficient for the overall use of the Application, but like anything new, it takes up more lines of code and GDI does require Memory to be used (though it's not a lot.)
For those that don't code and want 0MB of Memory use, it's quite impossible, especially when Graphics/Images are required to be used within the Application. Therefore by emptying the WorkingSet (which we do now) this reduces the memory to about 700KB, which on a system that has 4GB (4194304KB) is just a drop in the ocean, the same can be said for the FileSize!
Also don't forget this is AutoIt and when you consider the applications that are available that use AutoIt as the programming language, I think DropIt is on par with those programs that use C/C++. I have done my fair share of searching and with the AutoIt programs I have found many rarely add PNG Support, as this is not part of the "Standard Functions" within AutoIt. This requires some additional GDI++ knowledge
