Leaderboard

Haha ... feeling a noob here being directed to the Wiki to RTFM.

I have added a function to first try a lookup in the FileTable in memory for determining the required includefile. in case it is not found or not enabled, it will follow the old logic. It is available in the current beta zip file. Have a try and see if this makes it faster and all still works as desired.

I was in need of an IPC (Interprocess communication) between system, admin and user levels, and ended up writing this UDF to suit my wantings. Hope you find it useful too. Works from WinXP/Server2003 to the now current Win10/Server2016. It communicates between any mix of x32, x64, Admin, User. In the zip file, there is the UDF and an example: FMIPC(v0.2018.04.04).zip Special thanks to @RTFC for the help in the support forum

Introduction JSON is a pure data exchange format. Basically you only have to deal with JSON in 2 places in a program: Once when reading JSON data and once when outputting data. In between it should not really matter that the data used to be JSON or should be converted to it. You should not need any special intermediate structures but only the elements that the respective programming language provides anyway. This is exactly the approach of this UDF: There is the function _JSON_Parse(), which converts an arbitrary JSON string into (nested) pure AutoIt data types (Arrays, Maps, Strings, Numbers, Null, True, False). And on the other side we have the function _JSON_Generate(), which generates a JSON string from arbitrary (nested) AutoIt data structures. Import and export JSON So how to use - let`s give an example: Handling nested data structures JSON is often very nested. The resulting AutoIt data is therefore naturally also nested, which makes it somewhat cumbersome to process with pure AutoIt on-board methods. For this reason, the UDF comes with a few helper functions that make life with this data easier. One of them is _JSON_Get(), which allows you to access deeply nested data with a simple query syntax. On the other hand there is the function _JSON_addChangeDelete() with which you can (the name already says it) change, add and delete data. You can even easily create deeply nested structures with a single call. Again, here is a small example of how to use it: Strictly speaking, these functions should not even have "JSON" in their names, since they are generally applied to data structures in AutoIt. However, since they are often used in the JSON environment, we allow ourselves this small inaccuracy. Why should i give it a try? Probably the most common method to deal with JSON in AutoIt is the variant via JSMN. My minor dissatisfactions with this approach led me to write this UDF in the first place a few years ago. So the incentives are quite JSMN related: Parsing and extraction of data is faster than in JSMN. (Only if the JSON string makes heavy use of JSON escapes should JSMN be a bit faster in parsing, since the escapes are resolved later.) Editing the data is easier, because you don't need special commands for the JSMN intermediate structure but deal directly with AutoIt structures. Generating JSON is also simple: build your structure in AutoIt as you like and then let it generate a JSON string for you with _JSON_Generate(). The UDF is smaller (28kb vs. 45kb) The UDF is in pure AutoIt. You can directly customize any behavior as you like. >>sourcecode and download on github<<

Not when following the process I just described... but I will have look to see if we can use the generated FILE tables.

AutoItcomplete uses the cached tables of available/possible Functions/Variables, but the Jump function actually loop down the while tree of #included files to find it as it will ONLY jump to a Func/Var when really available for that script you are working in. You claim it changed ... I claim it didn't unless you can prove it!

And the user will be able to monitor and act upon a largish listview at high frequently refresh rate ? Rain man to the rescue!

The computer I tested is about 5 years old. the codec I used was "Xvid MPEG-4" which creates smaller files. I put everything together in a script, just the UDF made by Frank10 and the other one that you changed to make it easier to compare and thus try to remove the errors that occurred in the UDF that you changed.

Maybe this helps you:

Are you aware you can compile to exe? In your first post it looks like you are saying you leave full autoit scite at client location. Thats not needed. Protection to reverse engineering can be complex in any programming language.