therms

@InnI That's perfect, and that even helps me understand DllCall, so I really appreciate it a lot!

I need to get the scaling factor for each monitor in a multi-monitor setup on Windows 10. As far as I can find no one has posted anything like that here. I think this is probably what I need: https://msdn.microsoft.com/en-us/library/windows/desktop/dn280510(v=vs.85).aspx I'm just not a windows programmer and I haven't quite figured out how to use DLLCall to get the info from that function. Any pointers or help?

Open KeyPass, Open Options (Tools>Options), Select the "Interface" tab Make sure the second item ("Drop to background after copying data to the clipboard") is NOT checked. Run this: Local Const $hOptions = WinGetHandle("Options") Local Const $hTab = ControlGetHandle($hOptions, "", "[NAME:m_tabMain]") _GUICtrlTab_ClickTab($hTab, 2) You can change the tab index to any valid index, but no matter which tab is active and which tab you're switching to, that second item on the "Interface" tab gets automatically checked. Can anyone else reproduce this? Any ideas on a workaround? Any ideas whats actually happening? edit: Nevermind. Rebooting fixed whatever was happening here.

Updated source. Commit changelog. New features: histogram method creates a histogram out of a 1d or 2d array. display method uses _ArrayDisplay to display dict as a 2d array.

Nice! Thanks for pointing that out. Updated OP.

If you don't like dealing with Scripting.dictionary you might want to try out this thing I whipped up yesterday evening and this morning. Basically just a simple wrapper around Scripting.dictionary to make the API a little bit less stupid. By "stupid" I mean "not like the awesome Python dict API". Created for the following reasons.. Wanted to get a basic understanding of AutoItObject. Wanted to get a basic understanding of the Micro unit test framework. As of 11/4/2014 AutoIt Stable has no native dict or associative array type. A >Map type is in the current AutoIt beta. It's laborious to use Scripting.dictionary all the time. The Python dict API is better than Scripting.dictionary's I thought about writing my own hash table implementation in AutoIt, but on balance I decided it wasn't worth the effort and just stuck to Scripting.dictionary to save time/effort. As you can see I've got a decent number of unit tests for such a simple implementation, so it should be quite robust. #include <Dict2.au3> #include <Array.au3> $dict = _DictCreate() ConsoleWrite($dict.len()) ; Outputs 0 $dict.set("key1", "value1") $dict.set("key2", "value2") $dict.set("key3", "value3") $dict.set("key4", 1) ConsoleWrite($dict.get("key2")) ; Outputs 'value2' ConsoleWrite($dict.len()) ; Outputs 3 ConsoleWrite($dict.contains("key2") ; Outputs True $dict.set("key4", $dict.get("key4") + 1) ConsoleWrite($dict.get("key4")) ; Outputs 2 $dict.del("key4") ConsoleWrite($dict.contains("key4")) ; Outputs False $aPairs = $dict.pairs() _ArrayDisplay($aPairs) ; Displays 2d array with column one contains keys, and column two ; containing associated values $aKeys = $dict.keys() _ArrayDisplay($aKeys) ; Displays array containing all keys $aValues = $dict.values() _ArrayDisplay($aValues) ; Displays array of all values $aDesiredKeys = ["key1", "key3"] $aValues = $dict.values($aDesiredKeys) _ArrayDisplay($aValues) ; Displays array of values for key1 and key3 GET IT HERE

Nah, as I mentioned a few posts ago the problem has to do with using a standard user account.

I've used both the NSIS UAC plugin and the "finish install on first run of application" methods for installers I've wrote before. http://stackoverflow.com/questions/439932/getting-currently-logged-on-user-when-running-as-admin

Not a dumb question! I was using an au3 file.

Crossposting from another thread... OK, the issue is this: I use a standard user account. I double click the SciTE installer (version from site that says updated 8/1/2014). It pops up a UAC prompt. After that it installs all the config files in the appdata directory for the administrator account rather than as the standard user I'm logged in as. It also sets SCITE_USERHOME for the administrator, but not for the standard user. Obviously this is because of UAC, but I believe this is not best practice behavior for an installer. After manually copying the files to my standard user appdata directory and manually creating and setting to the right path the SCITE_USERHOME environment variable, I now have user calltips working.

OK, the issue is this: I use a standard user account. I double click the SciTE installer. It pops up a UAC prompt. After that it installs all the config files in the appdata directory for the administrator account rather than as the standard user I'm logged in as. It also sets SCITE_USERHOME for the administrator, but not for the standard user. Obviously this is because of UAC, but I believe this is not best practice behavior for an installer. After manually copying the files to my standard user appdata directory and manually creating and setting to the right path the SCITE_USERHOME environment variable, I now have user calltips working. Is there an issue tracker for the SciTE4AutoIt3 installer?

That file does not exist. In fact, when you told me to move au3.userudfs.properties and au3.user.calltips.api into that directory earlier it did not exist and I had to create it. The only thing in C:UsersThermsAppDataLocalAutoIt v3 was the Aut2exe directory. I assume that directory should be created on install or first start of SciTE. As a test, I just did an uninstall/install of SciTE again, and it did not create that folder. Even after starting it one time. Could this be because I run on a standard user account? I notice that that directory doe exists in my administrator accounts AppDataLocalAutoIT v3SciTE. My theory is that the installer handles installation on standard user accounts incorrectly. I'll try copying that folder over from my admin account and report back.

C:UsersThermsAppDataLocalAutoIt v3SCiTEau3.user.calltips.api: _TheFunctionOfAwesome($sOne, $sTwo) Writes two strings to stdout. (Requires: #include <deleteme.au3>) C:UsersThermsAppDataLocalAutoIt v3SCiTEau3.userudfs.properties:: au3.keywords.user.udfs=_thefunctionofawesome Still do not get autocomplete or syntax hints for function parameters.

Autoit: v3.3.12.0 SciTE: 3.4.4

I just know this is going to be something horrendously stupid on my part, but... I cannot get user calltips working in Scite. I uninstalled Scite. Using SciteConfig I made sure UDF folder was set to C:UsersThermsAutoITUDF. Using Sciteconfig I opened the User Calltips editor and added one function. The complete contents of C:UsersThermsau3.user.calltips.api: _TheFunctionOfAwesome($sOne, $sTwo) Writes two strings to stdout. (Requires: #include <deleteme.au3>) Contents of C:UsersThermsAutoITUDFdeleteme.au3: ; #FUNCTION# ==================================================================================================================== ; Name ..........: _TheFunctionOfAwesome ; Description ...: Writes two strings to stdout ; Syntax ........: _TheFunctionOfAwesome($sOne, $sTwo) ; Parameters ....: $sOne - A string value to output ; $sTwo - A string value to add to $sOne. ; Return values .: None ; Author ........: therms ; Modified ......: ; Remarks .......: This does stuff. ; Related .......: ; Link ..........: ; Example .......: No ; =============================================================================================================================== Func _TheFunctionOfAwesome($sOne, $sTwo) ConsoleWrite($sOne & $sTwo & @CRLF) EndFunc After closing and restarting Scite, create a new file C:UsersThermsDesktopdeleteme2.au3. Start file out with the requisite #include <deleteme.au3> and begin typing "_TheFunct" and Scite never suggests _TheFunctionOfAwesome!