Custom Query (3922 matches)

For scripts that use INI files, the option to create default INI values is desired. The current IniRead() function allows passing of a default value if specified section/key pair is absent. The requested enhancement would optionally create the specified section/key (and INI file, if necessary) with the default value if it does not exist.

This allows new script versions to add new INI parameters that will be written to an existing file, and allows automatic re-creation of a default INI file if no INI file is present. (Deleting an existing INI file would result in creation of a default INI.)

This feature could be implemented in one of two ways:

1) Adding an additional parameter to the AutoIt core after the "default" value that indicates whether the default value should be written to the INI file if it does not exist:

IniRead ( "filename", "section", "key", "default", "CREATE_OPTION" )

; CREATE_OPTION = TRUE/1 to write section/key/default to ini filename if it does not exist

2) Adding an _IniReadDefault() or similarly-named function to Misc.udf (or other) that writes the section/key/default to the ini filename if it does not exist.

If the feature is viable, and option 2 is preferred, a UDF function will be submitted. (Developer recommendations for the function name would be taken.)

Ref: Example Scripts, _ProcessListProperties() function ​http://www.autoitscript.com/forum/index.php?showtopic=70538

The _ProcessListProperties() function uses an SwbemRefresher object to get performance data for processes (CPU and MEM usage). If the function is called in a loop, there is a bad memory leak (monitored from Task Manager):

{{{HotKeySet("{ESC}", "_Quit")

; Loop to watch for memory leak While 1

_ProcessListProperties() Sleep(500)

WEnd

Func _Quit()

Exit

EndFunc ;==>_Quit }}}

Moving the creation of the SwbemRefresher outside the function (and loop) so it is only created once, makes the leak go away. (See topic post for code) ​http://www.autoitscript.com/forum/index.php?s=&showtopic=70538&view=findpost&p=566344

Removing all items and then releasing the object with $oRefresher.DeleteAll and $oRefresher = 0 does not change the memory leak.

I'm not sure if this is the right place to report forum issues. However, It appears that I have about 400K out of 1MB of upload space but zero attachments in the Manage Current Attachments drop-down. Where can I find / delete the file that is consuming space?