Jos

I've removed the compiled script as we don't want to distribute those. Users can compile the source themselves in case that is wanted. 🙂

I looked back and the last received file via PM was dec 10, but can't download that anymore to verify as it is unavailable (maybe server move). The last merged change was last month which resulted in the left window version: so pls PM me the correct version for these lines and I will merge them in. thanks, Jos

Ah ok... my bad, didn't see the first one, for some reason it jumped right away to your last message when I clicked the thread. I also don't know unless I didn't have a version with the latest changes? I have this uncommented on line 66 in AutoItIndentFix.lua: if (string.find(lText, "^[%s%t]") ~= nil) then so are we having a different file version?

I simply wasn't loading the saved udfs when swapping... last line 429 needed to be added: -- ======================================================================================= -- Update File au3.file.dynamic.calltips.api used by AutoComplete for this file -- ======================================================================================= local tNewAPIs = table.loadvar(props['AutoItDynamicIncludes.dynamic.file.APIs.' .. props['FilePath']]) props['au3.keywords.user.udfs'] = props['AutoItDynamicIncludes.user.udfs' .. props['FilePath']] it saves the previously found UDFs into memory for each open file, but that needs to be restored at tab change.

Is your fix also a one missing line thing? It's always easy once you know what is really happening when you know the exact steps to simulate it.

Think that one is also fixed in the latest beta version of AutoItDynamicIncludes.lua. pls give it a try. 🙂

I have noticed too that, when swapping between Opened files, it sometimes happens that UDFs are not colored anymore and you need to do a Save to get that back. So be my guest to do some debugging to see why that happens. 😉 The Volatile issue is fixed in the latest beta of AutoItDynamicIncludes.lua.

Why would you want to debug such long strings to an interaction output window? Won't logging the debug info to a log file make way more sense?

Hence I was very reluctant to give anything more than a pointer! 😉

... and yet there's again somebody feeding laziness and stimulating the "please barf code for me" requests......

What did you do, what were the results and what isn't working yet? .... as my crystal ball is broken.

So what did you do yourself this time, other than only ask a question again?

Just learn to add some consolewrite() statements for key variables to debug! Wild guess: wrong value in: $sFolder[0]

Then I've no idea why those reg entires are missing. The NSIS installer includes the steps to create them, so expect them to be there.

Are you running the installer on an account that doesnt have installer rights and have to specify another account to install it? mmm.. 🤔guess that can't be the reason as the reg key is HKLM...