ericnail Posted September 30, 2011 Posted September 30, 2011 Is it possible to save variables after exit and recall them on the next run? I am currently just saving vars to an INI File, however, I would like to do this without saving a file. Is there any way to do this? I've looked at EnvSet(), however, it deletes the env var after autoit exit. Thanks, Eric
Moderators Melba23 Posted September 30, 2011 Moderators Posted September 30, 2011 ericnail, You can put them into the registry - if you are brave enough! Look at RegWrite and RegRead in the Help file. M23 Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind Open spoiler to see my UDFs: Reveal hidden contents ArrayMultiColSort ---- Sort arrays on multiple columnsChooseFileFolder ---- Single and multiple selections from specified path treeview listingDate_Time_Convert -- Easily convert date/time formats, including the language usedExtMsgBox --------- A highly customisable replacement for MsgBoxGUIExtender -------- Extend and retract multiple sections within a GUIGUIFrame ---------- Subdivide GUIs into many adjustable framesGUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView itemsGUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeViewMarquee ----------- Scrolling tickertape GUIsNoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxesNotify ------------- Small notifications on the edge of the displayScrollbars ----------Automatically sized scrollbars with a single commandStringSize ---------- Automatically size controls to fit textToast -------------- Small GUIs which pop out of the notification area
ericnail Posted September 30, 2011 Author Posted September 30, 2011 On 9/30/2011 at 5:08 PM, Melba23 said: ericnail, You can put them into the registry - if you are brave enough! Look at RegWrite and RegRead in the Help file. M23 I might try.. What do you mean brave enough??
Moderators Melba23 Posted September 30, 2011 Moderators Posted September 30, 2011 ericnail, Quote What do you mean brave enough??Just my little joke - personally I try not to use the registry having had corruption problems in the distant past. M23 Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind Open spoiler to see my UDFs: Reveal hidden contents ArrayMultiColSort ---- Sort arrays on multiple columnsChooseFileFolder ---- Single and multiple selections from specified path treeview listingDate_Time_Convert -- Easily convert date/time formats, including the language usedExtMsgBox --------- A highly customisable replacement for MsgBoxGUIExtender -------- Extend and retract multiple sections within a GUIGUIFrame ---------- Subdivide GUIs into many adjustable framesGUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView itemsGUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeViewMarquee ----------- Scrolling tickertape GUIsNoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxesNotify ------------- Small notifications on the edge of the displayScrollbars ----------Automatically sized scrollbars with a single commandStringSize ---------- Automatically size controls to fit textToast -------------- Small GUIs which pop out of the notification area
MvGulik Posted September 30, 2011 Posted September 30, 2011 Register problems should not be that big of a problem now a days. Considering there are now all those nice virtual system tools. "Straight_and_Crooked_Thinking" : A "classic guide to ferreting out untruths, half-truths, and other distortions of facts in political and social discussions.""The Secrets of Quantum Physics" : New and excellent 2 part documentary on Quantum Physics by Jim Al-Khalili. (Dec 2014) "Believing what you know ain't so" ... Knock Knock ...
Unsigned Posted September 30, 2011 Posted September 30, 2011 (edited) The Registry is a good idea as long as you follow namespace conventions within it. I recommend using HKEY_CURRENT_USERSoftware{Vendor}{App} as your key, where {Vendor} and {App} are whatever you make them. HKEY_CURRENT_USERSoftware avoids permission problems as any user (admin or otherwise) should have write access to it. Secondly it's the Microsoft-approved area for application-specific configuration, which helps to minimize introducing any incompatibilities with future editions of Windows (provided you follow the {Vendor}{App} convention as well.) Edited May 31, 2012 by Unsigned .
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now