I want to present XMLWrapperEx.au3 - BETA Version

Want to join to the project ?

Here is some description:

; #INDEX# =======================================================================================================================
; Title .........: XMLWrapperEx.au3
; AutoIt Version : 3.3.10.2++
; Language ......: English
; Description ...: Functions to use for reading and writing XML using msxml.
; Remarks .......: BETA Version
; Author ........: mLipok
; Version .......: "1.1.1.01" ; _XML_MiscProperty_UDFVersion()

#CS
	This UDF is created on the basis of:
	https://www.autoitscript.com/forum/topic/19848-xml-dom-wrapper-com/
	For this reason, I attach also the last known (to me) previous version ($_XMLUDFVER = "1.0.3.98"  _XMLDomWrapper_1.0.3.98_CN.au3 )
	For the same reason I continue to recognize the achievements of the work of my predecessors (they are still noted in each Function header).
	.
	.
	.
	. !!!!!!!!! This is BETA VERSION (all could be changed) !!!!!!!!!
	.
	.
	.
	WORK IN PROGRES INFORMATION:
	For now 2015-09-01 the descripion (Function Header) can not entirely correctly describe the function.
	TODO: in many places I used "TODO" as a keyword to find what should be done in future
	.
	I want to: PREVENT THIS:
	The unfortunate nature of both the scripts is that the func return results are strings or arrays instead of objects.
	.
    I want to: USE THIS CONCEPT:
    .   All function should use Refernce to the object as first Function parameter
    .   All function should return in most cases objects. There should be separate functions to Change Object collection to array
    .   All function should use COM Error Handler in local scope.
    .   All function should return @error which are defined in #Region XMLWrapperEx.au3 - @ERROR Enums
    .    All function should have the same naming convention
    .    All variables should have the same naming convention
    .    There should not to be any Global Variable - exception is $g__oXMLDOM_Events
    .   It should be possible easy to use XML DOM Events
    .        https://msdn.microsoft.com/en-us/library/ms764697(v=vs.85).aspx
    .   It should be possible easy to Debug
    .    Ultimately, you should be able to do anything with your XML without having to use your own Error Handler.

#CE

More info inside zip archive.

This UDF can be downloaded from here:

REMARK:
This UDF was formerly named:   XMLWrapperEx.au3 

This is modifed version of _sql.au3 UDF.

For that I want to thanks : ; Chris Lambert, eltorro, Elias Assad Neto, CarlH

This is first public release , and still is as BETA

DOWNLOAD LINK (in download section): 

Have fun,

mLipok

EDIT: 2016-06-03
Below some interesting topics about databases:

EDIT 2016/07/04:
For more info about ADO look here:
https://www.autoitscript.com/wiki/ADO

FOR EXAMPLE DATABASE use AdventureWorksDW2016_EXT.bak from:
https://github.com/microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2016_EXT.bak
I will relay on this database in my examples.

Here is link to post which shows how "ODBC Data Source Administrator" looks like.

This UDF was created within the DarkMode UDF for AutoIt's Win32GUIs thread which was originally created by @NoNameCode. I ended up extending the features quite significantly and therefore decided to branch off into a new thread because I do not want to take anything away from the original DarkMode UDF.

Goal:

My goal was to make everything as automated and as simple as possible. I wanted it so that whoever is using it can just add one line of code _GUIDarkTheme_ApplyDark($hGUI, True) just before their already existing GUISetState() function. This would initiate the dark mode and automatically detect all controls, convert to dark mode and use the necessary subclassing whenever needed.

Community:

This UDF contains a lot of code from throughout the amazing AutoIt community and therefore belongs to every single one of us. I am always welcome to any suggestions and collaboration.

Note:

This UDF requires Windows 10/11 or higher due to API being used and lack of necessary theme functionality on older versions of Windows. Running this UDF on the latest versions of Windows 11 are always going to produce the best results. Windows 10 is missing some of the theme resources and therefore more subclassing is done there. Windows 11 also has newer and improved theme resources, particularly in 24H2/25H2 builds and higher.

Changelog:

GUIDarkTheme-2026.07.05.zip

GUIDarkTheme-2026.07.10.zip

GUIDarkTheme-2026.07.11.zip

; #INDEX# ========================================================================
; Title .........: TeamViewer.au3
; AutoIt Version : 3.3.10.2++
; Language ......: English
; Description ...: A collection of function for use with TeamViewer API
; Author ........: mLipok
; Modified ......:
; URL ...........:
; URL ...........: https://www.teamviewer.com/
; URL ...........: https://www.teamviewer.com/en/integrations/
; URL ...........: https://integrate.teamviewer.com/en/develop/api/get-started/
; URL ...........: https://downloadeu1.teamviewer.com/integrate/TeamViewer_API_Documentation.pdf
; Remarks .......: This UDF was created based on TeamViewer_API_Documentation.pdf v 1.4.1
; Remarks .......: This UDF is using Free Chilkat component look here https://www.autoitscript.com/forum/files/file/433-chilkat-udf/
; Remarks .......: Documentation is "work in progress"
; Date ..........: 2017/02/08
; Version .......: 0.1.1 BETA - Work in progress
; ================================================================================

in TeamViewer_Example.au3 you can see few examples:

 

Func _Example()

	; If not exist then create new INI file from template
	If Not FileExists('TeamViewer_Example.ini') Then FileCopy('TeamViewer_Example — Template.ini', 'TeamViewer_Example.ini')

	; Read Access Token from INI
	Local $sTV_AccessToken = IniRead('TeamViewer_Example.ini', 'Settings', 'AccessToken', '')
	If $sTV_AccessToken = '' Then
		; Your Access Token, can be left empty when OAuth (below) is configured.

		; ClientId = <-----------------	Create an app in your TeamViewer Management Console and insert the client ID to the INI
		; ClientSecret = <------------- Insert your client secret to the INI
		; AuthorizationCode = <--------	Visit https://webapi.teamviewer.com/api/v1/oauth2/authorize?response_type=code&client_id=YOUR$i_ClientIdHERE
		; 								Login, grant the permissions (popup) and put the code shown in the AuthorizationCode variable to the INI

		Local $sTVOAuth_ClientID = IniRead('TeamViewer_Example.ini', 'OAuth2', 'ClientID', '')
		Local $sTVOAuth_ClientSecret = IniRead('TeamViewer_Example.ini', 'OAuth2', 'ClientSecret', '')

		_IECreate('https://webapi.teamviewer.com/api/v1/oauth2/authorize?response_type=code&client_id=' & $sTVOAuth_ClientID)
		; Local $sTVOAuth_AuthorizationCode = IniRead('TeamViewer_Example.ini', 'OAuth2', 'authorizationCode', '')
		Local $sTVOAuth_AuthorizationCode = InputBox('AuthorizationCode', 'Please provide TV OAuth2 AuthorizationCode')
		If @error Then Return

		If $sTVOAuth_ClientID Then $sTV_AccessToken = _TVAPI_RequestOAuth2_AccessToken($sTVOAuth_ClientID, $sTVOAuth_ClientSecret, $sTVOAuth_AuthorizationCode)
	EndIf

	If $sTV_AccessToken Then _TVAPI_AccessToken($sTV_AccessToken)

	If _TVAPI_Ping() = True Then ; ping API to check connection and $sTV_AccessToken
		_Example_TeamViewer__1_Devices_SaveToFile()
;~ 		_Example_TeamViewer__2_Devices_ChangeDetails()
;~ 		_Example_TeamViewer__3_Devices_GetDevicesSingleID()
;~ 		_Example_TeamViewer__4_Reports_GetAllConnections()
;~ 		_Example_TeamViewer__5_Users_GetUserInfomation()
;~ 		_Example_TeamViewer__6_Groups_ListGroups()
;~ 		_Example_TeamViewer__7_Devices_AddDeleteDevice()
	Else
		MsgBox(0, '_TVAPI_Ping', "$v_Token or connection problem.")
	EndIf
EndFunc   ;==>_Example

You can download it here:

I'm using TeamViewer_Example.ini to store my secret tokens/keys.

[Settings]
AccessToken=

[OAuth2]
ClientID=
ClientSecret=
authorizationCode=

I've found I need quizzing software that works like the old Transdumper software. (You can find it here: https://www.gejos.com/) 

The problem with that software is it runs in Internet Explorer and needs ActiveX. Edge doesn't use that unless you run the browser in IE mode. Even then, Trandumper doesn't work in it. Been there, tried to get it to work, got the t-shirt.... and the juice isn't worth the squeeze. I looked at a bunch of other apps out there and it is either super pricey, crippled in features, very clunky to use, or just doesn't do what I need. 

So, I decided to dust off my AutoIt skills and build an app that can do it. 

I'm looking to get most of the the basic functionality of Trandumper in a GUI, use CSV files to store the test, and keep it simple. I don't see it working on mobile and have no plans to do that. I won't have drag and drop support either. Other than that, I should be able to get it to work. 

If anyone is interested in helping me code this thing, I would be grateful. Thanks in advance. 

I’m not sure if there is much need nor desire for this little project, but I thought I would share it in case there is.

These themes are an attempt to copy over the themes that come with Scite4AutoIt. Being that there are many further customizations available for VS Code compared to Scite, many colorations in VS Code may not match, and these may not be as well combined as they are in Scite, as VS Code colorizes things slightly different from Scite in some instances.

Because of the vast number of available settings and tokens for each language, it has been thought best to only have these custom themes apply to AutoIt files. I have used the token names from the two leading AutoIt extensions that are currently available, published by LoganCH and Genius257, consequently, if neither is installed or activated AutoIt syntax highlighting will be defaulted to VS code colorings. When the user opens any other language file, the theme coloring will revert to the base theme's colorization for tokens (see Read-Me chart), but the editor colors (background, similar word highlight, etc.) will not.

The vsix file can be downloaded from the following, as I do not intend to publish these on the marketplace: https://github.com/donnyh13/Scite4AutoIt_Themes/releases

The base themes are three themes included with VS Code: VS Code Light, VS Code Dark, and Monokai, which are all MIT licensed, and belong to the respective owner(s). Copyright (c) Microsoft Corporation.

All Scite Themes, colorings and names are owned by the developers of Scite4AutoIt, and the respective theme creators, and I claim no ownership to any of them.

If any of the theme owners wish for these to be removed, please let me know.

Note

For those users on older Windows versions, and unable to update VS Code to later versions, the following should be noted. The extension created by LoganCH became incompatible from version 1.0.14+ with Vs Code 1.70.3, (the latest available on Windows 7). In Logan's versions 1.4.0, and 1.5.0 there were several modifications and additions that make tokenization better, and cleaner, which users on older systems will not be able to benefit from. As a possible work around, see below.

As of the time of writing (May, 2026), Genius257's extension (v1.8.9) is still compatible with VS Code 1.70.3, and does not present these issues.

Possible Workaround

Being under the above limitations myself, I have found the following workaround. Any users with some coding experience can follow the following steps at their own risk. These directions work for Logan's version 1.5.0. I make no guarantee it will work with later versions.

1.  Download a copy of Logan's extension files from his GitHub, or, minimally, a copy of the file autoit.tmLanguage.json, found in the syntaxes file. (Make sure to get the file with the .json extension).
2. Locate your VS Code extensions folder, mine was found at the following location:
    C:\Users\Owner\.vscode\extensions
3. Make a copy of Logan's extension folder somewhere else, in case something goes wrong. The extension folder is named: damien.autoit-1.0.13 or similar.
4. Open Logan's extension folder found in the VS Code extension folder (not the copy you made).
5. Find and open the package.json file.

• 5.1. Inside the package.json file, find the following line, (Mine was around line 225):

"grammars": [
			{
				"language": "autoit",
				"scopeName": "source.autoit",
				"path": "./syntaxes/autoit.tmLanguage"
			},
			{
				"language": "vscode-autoit-output",
				"scopeName": "source.vscode_autoit_output",
				"path": "syntaxes/vscode-autoit-output.tmLanguage.json"
			}
		],

• 5.2. Edit the "path" line for "language": "autoit"
• From:

"path": "./syntaxes/autoit.tmLanguage"

• To:

"path": "./syntaxes/autoit.tmLanguage.json"

• 5.3. Save and close the file.

6. Navigate to inside the Syntaxes folder.

7. Copy the new autoit.tmLanguage.json file into this folder, replacing the existing file, if present.

8. Close VS Code if open, and open an AutoIt Script in VS Code to make sure everything is colorized properly, and that no errors are present.

Previews

Standard

Old-Standard

Old-LCD

MSDEV

MSDEV2

Dark

Monokai

Twilight

You have measurements. They don't perfectly agree. You need the best answer.

Least squares adjustment finds the optimal values from redundant, contradictory observations — and tells you exactly how reliable the results are. It's the mathematical foundation behind positioning, navigation, calibration, curve fitting, regression, signal processing, and virtually any domain where measurements meet reality.

This UDF brings that capability to AutoIt with a radically simple interface: describe your model as string formulas, add measurements with their uncertainties, and call _adj_solve(). No matrix algebra, no numerical recipes, no external tools — just your problem and your data.

Underneath, it's a complete adjustment engine powered by OpenBLAS, with nonlinear iterative solvers, variance component estimation, robust estimators, and full statistical diagnostics — the kind of tooling normally reserved for MATLAB or specialized scientific software.

Download: Latest Release on GitHub
GitHub: https://github.com/Sylvan86/autoit-adjustment-udf

Quick Start

#include "Adjustment.au3"
; 5 measurements of a distance — find the best estimate and accuracy

Local $mSystem = _adj_createSystem()

_adj_addObsFunction($mSystem, "M1", "X", 10.02, 1.0)
_adj_addObsFunction($mSystem, "M2", "X",  9.98, 1.0)
_adj_addObsFunction($mSystem, "M3", "X", 10.01, 1.0)
_adj_addObsFunction($mSystem, "M4", "X", 10.03, 1.0)
_adj_addObsFunction($mSystem, "M5", "X",  9.99, 1.0)
_adj_setInitialValue($mSystem, "X", 10.0)

_adj_solve($mSystem)

ConsoleWrite(_adj_displayResults($mSystem))
; Result: X = 10.006 ± 0.009

This is just the simplest case — a mean value. The real strength lies in simultaneously adjusting different measurements with different formulas. For example, determining a point's position from distance and direction measurements, or fitting a curve to data while enforcing constraints.

Feature Overview

For experts — the full scope of the UDF:

Model Types

• OLS / WLS / GLS — Overdetermined system (weighted, generalized with full covariance matrix)
• LSE / WLSE / GLSE — With parameter constraints
• CLS / WCLS / GCLS — Condition adjustment
• GLM / WGLM / GGLM — Gauss-Helmert model (most general form)

Model type detection is automatic based on the input structure.

Solvers and Iteration Methods

• Iteration method: Gauss-Newton, Levenberg-Marquardt (Nielsen damping)
• Linear solver: QR decomposition (DGELSY), Singular Value Decomposition (DGELSD)
• Jacobian matrices: Numerical (Central, Forward, Backward, Ridder, Higham) or analytical
• Scaling: Jacobi equilibration (automatic column scaling)

Statistics and Diagnostics

• Basic statistics: A posteriori variance factor s0², degrees of freedom, vTPv
• Accuracy: Cofactor matrix Qxx, standard deviations (parameters, observations)
• Controllability: Redundancy numbers r_i, cofactor matrices Qvv and Qy
• Model validation: Global test (Chi²)
• Outlier diagnostics: Baarda test (w-statistic), Pope test (tau-statistic), p-values, MDB

Variance Component Estimation (VCE)

Helmert method: Separate variance factors for different observation groups (e.g. distances vs. angles). Iterative until convergence.

Robust Estimation (IRLS)

• L1 (Median) — Breakdown point: 50%
• Huber (c = 1.345) — Breakdown point: ~5%
• Hampel (a = 1.7, b = 3.4, c = 8.5) — Breakdown point: ~25%
• Biweight (Tukey) (c = 4.685) — Breakdown point: 50%
• BIBER (Schweppe) (c = 3.5) — Breakdown point: leverage-dependent
• Modified-M (Koch) (c = 1.5) — Breakdown point: leverage-dependent

Scale parameters: MAD, s0, a priori, user-defined.

Additional Features

• Symbolic formula input as strings — parameters and observations are detected automatically
• Compute-on-demand — statistics are only calculated when requested
• Configurable result display with selectable columns and sections
• Outlier detection and removal (_adj_getOutliers, _adj_removeObs)

Installation

Requirements:

• AutoIt v3.3.16+ (x64)
• OpenBLAS DLL (libopenblas_x64.dll)

Setup:

1. Download: Get the latest release from GitHub Releases
2. Extract: Unpack the files into a directory
3. OpenBLAS: The libopenblas_x64.dll is downloaded automatically on first run, or can be placed manually in the UDF directory
4. Include:

$__g_hBLAS_DLL = DllOpen("libopenblas_x64.dll")
#include "Adjustment.au3"

Documentation

The full documentation is available on GitHub:

• Tutorial — Step-by-step guide, 9 chapters (Beginners)
• Feature Overview — Full capabilities at a glance (Everyone)
• API Reference — All 17 public functions (Developers)
• Configuration — Solver, display, and robust config (Advanced)
• Result Structure — All keys of the result map (Advanced)
• Model Types — OLS to GGLM with mathematics (Experts)
• Solvers — GN, LM, QR, SVD in detail (Experts)
• Statistics — s0, Qxx, global test, Baarda/Pope (Experts)
• Robust Estimation — IRLS, 6 estimators, weight functions (Experts)
• Error Codes — All $ADJ_ERR_* with solutions (Everyone)

Tutorial Chapters

1. Getting Started — What is adjustment?
2. First Network — Trilateration
3. Weighting — Accounting for measurement precision
4. Mixed Observations — Combining distances and angles
5. Constraints — Restrictions and fixed parameters
6. Regression — OLS, orthogonal, Deming, York
7. Covariance Matrix — Correlated measurements
8. Understanding Results — Configuring and interpreting output
9. Robust Estimation — Handling outliers

Download

>>> Download the latest release from GitHub <<<

Source code and issue tracker: https://github.com/Sylvan86/autoit-adjustment-udf
 

You check out the extension on the VSCode Marketplace here and view the code on GitHub here.

Edit:

Go to http://code.visualstudio.com/docs/setup/windows for information on installing Visual Studio Code.

See http://code.visualstudio.com/docs/editor/extension-gallery for information on installing extensions to VS Code.

Original TO DO List:

Current TO DO List:

• Add TreeView/ListView context menu items  similar to what the menubar has
• Add ability to create new files and folders (uses templates)
• Run IFileOperation::MoveItems and IFileOperation::CopyItems in a separate process
  • Needs to use IPC to communicate
  • Need to send data object to the other process
  • Or alternatively send array of file names and create data object in the other process
• Subclass the menu bar for dark mode (and get rid of ModernMenuRaw UDF)
  • This is likely a big job and lower priority
• Implement autoscrolling of TreeView/ListView during drag and drop (reference)

If anyone wants to contribute, maybe we should just let each other know what part we are working on so that we don't have two people working on the same thing.

Latest Source Code Release: Releases (latest)

Latest Changes: CHANGELOG

Sometimes you wish critical parts of your AutoIt script could run at native speed - tight loops, numerical algorithms, or bit-level operations that AutoIt simply wasn't designed for. JIT.au3 lets you write C code as a string, compile it at runtime, and call it directly from AutoIt.

No compiler installation required. All you need is this UDF and an internet connection.
The compilation is handled by the Compiler Explorer (Godbolt) API - the compiled machine code is loaded into executable memory and made callable via DllCallAddress.

GitHub: https://github.com/Sylvan86/autoit-jit-udf
Download: Releases

Quick Start

#include "JIT.au3"

; Write C code - prefix exported functions with CALLCONV
Global $sCode = _
    'CALLCONV double doubleIt(double x) {' & @LF & _
    '    return x * 2.0;                 ' & @LF & _
    '}'

; Compile via Godbolt API
Global $mCode = _JIT_Compile($sCode)

; Call the compiled function
Global $aResult = DllCallAddress("double", $mCode.ptr + $mCode.Funcs["doubleIt"], "DOUBLE", 21.0)
ConsoleWrite("Result: " & $aResult[0] & @CRLF)  ; → 42.0

; Free memory when done
_JIT_Free($mCode)

Compile Once, Reuse Forever

Quote

Please treat the Godbolt API with respect.

The Compiler Explorer is a free community project. Every call to _JIT_Compile sends a request to their servers. (unless you have explicitly chosen a different instance - what`s possible)

After the first successful compilation, save the binary string and reuse it - no further API calls needed and much faster startup:

; First run: compile and note the ReusableString
Global $mCode = _JIT_Compile($sCode)
ConsoleWrite($mCode.ReusableString & @CRLF)  ; → save this string
_JIT_Free($mCode)

; All subsequent runs: load from saved ReusableString (no internet needed!)
Global $mCode = _JIT_LoadBinary('{"b":"8g9YwMM","f":{"doubleIt":0}}')
Global $aResult = DllCallAddress("double", $mCode.ptr + $mCode.Funcs["doubleIt"], "DOUBLE", 21.0)

See examples/example_reuse.au3 in the repository for a complete walkthrough.

API Overview

• _JIT_Compile($sCode) - Compile C code and return executable memory
• _JIT_LoadBinary($sBinary) - Load a previously compiled binary (no API call)
• _JIT_Free($mCode) - Release allocated executable memory
• _JIT_SetServer(...) - Configure server, compiler, language, proxy
• _JIT_GetCompilers() - List available compilers
• _JIT_GetLanguages() - List available languages
• _JIT_DescribeOpcode($sOp) - Get description of an assembler opcode

Limitations

This UDF is designed for small, self-contained code snippets - not for full C projects.

• No #include support - the C standard library is not available. There is no linker; the code must be fully self-contained.
• No math.h functions - sin(), cos(), pow() etc. require libm which is not linked. Some GCC __builtin_* functions work as inline alternatives (see examples/example_builtins.au3).
• Internet required for compilation - use _JIT_LoadBinary to work offline after the first compile.
• Single translation unit - all code must be in one string, no multi-file compilation.

Examples

The repository includes five examples:

• example_scalar.au3 - Basic principle: compile and call a simple function
• example_array.au3 - Pass an array to Kahan summation vs. naive summation
• example_string.au3 - String processing: alternating case transformation
• example_builtins.au3 - GCC __builtin_* functions: what works, what doesn't
• example_reuse.au3 - Save and reload compiled binaries for offline use

Dependencies

• JSON.au3 - JSON UDF for API communication (included in release download)

Acknowledgements

This project would not be possible without the Compiler Explorer (Godbolt) by Matt Godbolt and contributors. It is an incredible open-source tool for the programming community. Please use their API responsibly.

I am using AutoIt to automate my Electron application. Everything worked well with an older version of Electron and Chromedriver. However, since I upgraded to the new Electron version (v40.0.0, available here: https://github.com/electron/electron/releases/tag/v40.0.0), I can no longer use Chromedriver to control the application. Nothing works anymore.

Here is an example of the code I am using to launch the application:

_WD_Option('Driver', $waytochromedriver)
_WD_Option('Port', 9515)
_WD_Option('DriverParams', '--verbose --log-path="' & @ScriptDir & '\chrome.log"')
_WD_CapabilitiesStartup()
_WD_CapabilitiesAdd('alwaysMatch', 'chrome')
_WD_CapabilitiesAdd('excludeSwitches', 'enable-automation')
_WD_CapabilitiesAdd('w3c', True)
_WD_CapabilitiesAdd('useAutomationExtension', False)
_WD_CapabilitiesAdd('binary','ELECTRON.exe')
$sDesiredCapabilities = _WD_CapabilitiesGet()

; Launching the WebDriver console
_WD_Startup()

; Requesting the creation of a new session from the WebDriver
$sSession = _WD_CreateSession($sDesiredCapabilities)

; Waiting 50 seconds for the ELECTRON window to appear
WinWait("ELECTRON", "", 50)

Do you have any advice or feedback to make Chromedriver work with Electron v40?
Is there a specific configuration needed, or a particular version of Chromedriver required?

Thank you in advance for your help!

I've tried the existing ones, and found small problems that i felt i could improve on, but it would require an entire new approach to the inner working of the existing extensions.

Also working on a complete AutoIt3 parser a vscode extension just made sense

Any feedback is appreciated, and i hope this project will benefit more than just me 🤡

Visual Studio Code Marketplace

GitHub repo

Some of the current features:

• Basic AutoIt2 syntax highlighting, for fun 🤡
• AutoIt3 syntax highlighting
• Variable/Function hover gives declaration information if available.
• Goto declaration
• #include links
• Syntax checking, as you type
• Function signature help
• Function and variable list in a file via the outline tab.
• Works on desktop (any OS) and web version

⚠️ The parser used is not yet 100% complete (see issues for know problems), and the last thing to be implemented is the With code block.

Hope you like 😃

Is there any way to use .NET DLL libraries with AutoIt? I happen to have one that'd have made my life easier, but DLLCall() returns an error: no functions with such name found. Searching and reading forums made me think that's not a fault of a library. I've used yashied's DLL Helper, but it didn't return any function names as well.

Thanks!

Here are links to information/documentation:

Image comes from: https://docs.microsoft.com/en-us/microsoft-edge/webview2/media/webview2/whatwebview.png

Introduction to Microsoft Edge WebView2
https://docs.microsoft.com/en-us/microsoft-edge/webview2/

Understand WebView2 SDK versions
https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/versioning

Quote

• Win32 C/C++. When using QueryInterface to obtain a new interface, check for a return value of E_NOINTERFACE. This value may indicate that the WebView2 Runtime is a previous version, and doesn't support that interface.

Download:
https://developer.microsoft.com/en-US/microsoft-edge/webview2/
https://developer.microsoft.com/en-US/microsoft-edge/webview2/#download-section
https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution

API Reference:
https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/?view=webview2-1.0.622.22

HowTo/Concepts:
https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/versioning
https://docs.microsoft.com/en-us/microsoft-edge/webview2/gettingstarted/win32
https://docs.microsoft.com/en-us/microsoft-edge/webview2/howto/debug?tabs=devtools
https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/security
https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/userdatafolder

https://mybuild.microsoft.com/sessions/9198aeac-0c8e-4d32-96d1-cbb99a390aa6

Example:
https://github.com/MicrosoftEdge/WebView2Samples

Related:

https://www.essentialobjects.com/Products/WebBrowser/Default.aspx?gclid=CjwKCAiA17P9BRB2EiwAMvwNyMe6UI9VHej-JYDBUoyGDFz40KaaJ_RidY-75Fhr-PHz65sSVC0XlxoC5loQAvD_BwE

https://docs.microsoft.com/en-us/microsoft-edge/webview2/howto/webdriver

btw.
I'm not WindowsApi expert (QueryInterface, C++, DllCall).
What I trying to say is:     It means that I do not done anything in this regards .... as so far.

TIMELINE/ChangeLog:
 

1. 2020-11-12 - Project propsed by @mLipok
2. 2021-02-03 - First version provided by @LarsJ

https://learn.microsoft.com/en-us/windows/win32/medfound/microsoft-media-foundation-sdk

Here a working take on playback.

#include <StructureConstants.au3>
#include <GUIConstants.au3>
#include <Array.au3>

Opt("MustDeclareVars", True)

Global Const $MF_VERSION = 0x00020070
Global Enum $MFSTARTUP_FULL, $MFSTARTUP_LITE
Local $aCall, $iHresult

$aCall = DllCall("Mfplat.dll", "long", "MFStartup", "long", $MF_VERSION, "long", $MFSTARTUP_FULL)

$aCall = DllCall("Mf.dll", "long", "MFCreateMediaSession", "ptr", 0, "ptr*", 0)
Local $pIMFMediaSession = $aCall[2]

Global Const $sIID_IMFMediaEventGenerator = "(2cd0bd52-bcd5-4b89-b62c-eadc0c031e7d)"
Global Const $tag_IMFMediaEventGenerator = _
    "GetEvent hresult(long; ptr*);" & _
    "BeginGetEvent hresult(ptr; ptr);" & _
    "EndGetEvent hresult(ptr; ptr*);" & _
    "QueueEvent hresult(uint; struct*; hresult; struct*);"

Global Const $sIID_IMFMediaSession = "{90377834-21d0-4dee-8214-ba2e3e6c1127}"
Global Const $tag_IMFMediaSession = $tag_IMFMediaEventGenerator & _
    "SetTopology hresult(uint; ptr);" & _
    "ClearTopologies hresult();" & _
    "Start hresult(struct*; struct*);" & _
    "Pause hresult();" & _
    "Stop hresult();" & _
    "Close hresult();" & _
    "Shutdown hresult();" & _
    "GetClock hresult(ptr*);" & _
    "GetSessionCapabilities hresult(uint*);" & _
    "GetFullTopology hresult(uint; uint64; ptr*);"

Local $oIMFMediaSession = ObjCreateInterface($pIMFMediaSession, $sIID_IMFMediaSession, $tag_IMFMediaSession)
ConsoleWrite("oIMFMediaSession " & IsObj($oIMFMediaSession) & @CRLF)

$aCall = DllCall("Mfplat.dll", "long", "MFCreateSourceResolver", "ptr*", 0)
Local $pIMFSourceResolver = $aCall[1]
Global Const $sIID_IMFSourceResolver = "{fbe5a32d-a497-4b61-bb85-97b1a848a6e3}"
Global Const $tag_IMFSourceResolver = _
    "CreateObjectFromURL hresult(wstr; uint; ptr; long*; ptr*);" & _
    "CreateObjectFromByteStream hresult(ptr; wstr; uint; ptr; long*; ptr*);" & _
    "BeginCreateObjectFromURL hresult(wstr; uint; ptr; ptr*; ptr; ptr);" & _
    "EndCreateObjectFromURL hresult(ptr; long*; ptr*);" & _
    "BeginCreateObjectFromByteStream hresult(ptr; wstr; uint; ptr; ptr*; ptr; ptr);" & _
    "EndCreateObjectFromByteStream hresult(ptr; long*; ptr*);" & _
    "CancelObjectCreation hresult(ptr);"

Local $oIMFSourceResolver = ObjCreateInterface($pIMFSourceResolver, $sIID_IMFSourceResolver, $tag_IMFSourceResolver)
ConsoleWrite("oIMFSourceResolver " & IsObj($oIMFSourceResolver) & @CRLF)

Global Const $MF_RESOLUTION_MEDIASOURCE = 1
Global Enum $MF_OBJECT_MEDIASOURCE, $MF_OBJECT_BYTESTREAM, $MF_OBJECT_INVALID
Local $iObjType, $pMediaSource

Local $hResult = $oIMFSourceResolver.CreateObjectFromURL(@ScriptDir & "\Relax.mp4", $MF_RESOLUTION_MEDIASOURCE, 0, $iObjType, $pMediaSource)

Global Const $sIID_IMFMediaSource = "{279a808d-aec7-40c8-9c6b-a6b492c78a66}"
Global Const $tag_IMFMediaSource = $tag_IMFMediaEventGenerator & _
    "GetCharacteristics hresult(uint*);" & _
    "CreatePresentationDescriptor hresult(ptr*);" & _
    "Start hresult(ptr; struct*; struct*);" & _
    "Stop hresult();" & _
    "Pause hresult();" & _
    "Shutdown hresult();"
Local $oIMFMediaSource = ObjCreateInterface($pMediaSource, $sIID_IMFMediaSource, $tag_IMFMediaSource)
ConsoleWrite("oIMFMediaSource " & IsObj($oIMFMediaSource) & @CRLF)
Local $pIMFPresentationDescriptor
$oIMFMediaSource.CreatePresentationDescriptor($pIMFPresentationDescriptor)

Global Const $sIID_IMFAttributes = "(2cd2d921-c447-44a7-a13c-4adabfc247e3)"
Global Const $tag_IMFAttributes = _
    "GetItem hresult(struct*; struct*);" & _
    "GetItemType hresult(struct*; long*);" & _
    "CompareItem hresult(struct*; struct*; bool*);" & _
    "Compare hresult(ptr; long; bool*);" & _
    "GetUINT32 hresult(struct*; uint*);" & _
    "GetUINT64 hresult(struct*; uint64*);" & _
    "GetDouble hresult(struct*; double*);" & _
    "GetGUID hresult(struct*; struct*);" & _
    "GetStringLength hresult(struct*; uint*);" & _
    "GetString hresult(struct*; wstr; uint; uint*);" & _
    "GetAllocatedString hresult(struct*; wstr*; uint*);" & _
    "GetBlobSize hresult(struct*; uint*);" & _
    "GetBlob hresult(struct*; struct*; uint; uint*);" & _
    "GetAllocatedBlob hresult(struct*; ptr*; uint*);" & _
    "GetUnknown hresult(struct*; struct*; ptr*);" & _
    "SetItem hresult(struct*; struct*);" & _
    "DeleteItem hresult(struct*);" & _
    "DeleteAllItems hresult();" & _
    "SetUINT32 hresult(struct*; uint);" & _
    "SetUINT64 hresult(struct*; uint64);" & _
    "SetDouble hresult(struct*; double);" & _
    "SetGUID hresult(struct*; struct*);" & _
    "SetString hresult(struct*; wstr);" & _
    "SetBlob hresult(struct*; struct*; uint);" & _
    "SetUnknown hresult(struct*; ptr);" & _
    "LockStore hresult();" & _
    "UnlockStore hresult();" & _
    "GetCount hresult(uint*);" & _
    "GetItemByIndex hresult(uint; struct*; struct*);" & _
    "CopyAllItems hresult(ptr);"

Global Const $sIID_IMFPresentationDescriptor = "{03cb2711-24d7-4db6-a17f-f3a7a479a536}"
Global Const $tag_IMFPresentationDescriptor = $tag_IMFAttributes & _
    "GetStreamDescriptorCount hresult(uint*);" & _
    "GetStreamDescriptorByIndex hresult(uint; bool*; ptr*);" & _
    "SelectStream hresult(uint);" & _
    "DeselectStream hresult(uint);" & _
    "Clone hresult(ptr*);"

Local $oIMFPresentationDescriptor = ObjCreateInterface($pIMFPresentationDescriptor, $sIID_IMFPresentationDescriptor, $tag_IMFPresentationDescriptor)
ConsoleWrite("oIMFPresentationDescriptor " & IsObj($oIMFPresentationDescriptor) & @CRLF)

; CreatePlaybackTopology

Local $hWnd = GUICreate("Basic Playback", 800, 600, -1, -1, $WS_OVERLAPPEDWINDOW)
; register msg

Global Const $sIID_IMFTopology = "{83cf873a-f6da-4bc8-823f-bacfd55dc433}"
Global Const $tag_IMFTopology = $tag_IMFAttributes & _
  "GetTopologyID hresult();" & _
  "AddNode hresult(ptr);" & _
  "RemoveNode hresult();" & _
  "GetNodeCount hresult();" & _
  "GetNode hresult();" & _
  "Clear hresult();" & _
  "CloneFrom hresult();" & _
  "GetNodeByID hresult();" & _
  "GetSourceNodeCollection hresult();" & _
  "GetOutputNodeCollection hresult();"

$aCall = DllCall("Mf.dll", "long", "MFCreateTopology", "ptr*", 0)
Local $pIMFTopology = $aCall[1]
Local $oIMFTopology = ObjCreateInterface($pIMFTopology, $sIID_IMFTopology, $tag_IMFTopology)
ConsoleWrite("oIMFTopology " & IsObj($oIMFTopology) & @CRLF)

Local $iCount, $bSelect, $pIMFStreamDescriptor, $oIMFStreamDescriptor
$oIMFPresentationDescriptor.GetStreamDescriptorCount($iCount)
Global Enum $MF_TOPOLOGY_OUTPUT_NODE, $MF_TOPOLOGY_SOURCESTREAM_NODE, $MF_TOPOLOGY_TRANSFORM_NODE, $MF_TOPOLOGY_TEE_NODE, $MF_TOPOLOGY_MAX = 0xFFFFFFFF
Global Const $sIID_IMFTopologyNode = "{83cf873a-f6da-4bc8-823f-bacfd55dc430}"
Global Const $tag_IMFTopologyNode = $tag_IMFAttributes & _
  "SetObject hresult(ptr);" & _
  "GetObject hresult();" & _
  "GetNodeType hresult();" & _
  "GetTopoNodeID hresult();" & _
  "SetTopoNodeID hresult();" & _
  "GetInputCount hresult();" & _
  "GetOutputCount hresult();" & _
  "ConnectOutput hresult(dword;ptr;dword);" & _
  "DisconnectOutput hresult();" & _
  "GetInput hresult();" & _
  "GetOutput hresult();" & _
  "SetOutputPrefType hresult();" & _
  "GetOutputPrefType hresult();" & _
  "SetInputPrefType hresult();" & _
  "GetInputPrefType hresult();" & _
  "CloneFrom hresult();"
Global Const $MF_TOPONODE_SOURCE = __COM_CreateGUID("{835c58ec-e075-4bc7-bcba-4de000df9ae6}")
Global Const $MF_TOPONODE_PRESENTATION_DESCRIPTOR = __COM_CreateGUID("{835c58ed-e075-4bc7-bcba-4de000df9ae6}")
Global Const $MF_TOPONODE_STREAM_DESCRIPTOR = __COM_CreateGUID("{835c58ee-e075-4bc7-bcba-4de000df9ae6}")
Global Const $MFMediaType_Audio = __COM_CreateGUID("{73647561-0000-0010-8000-00aa00389b71}")
Global Const $MFMediaType_Video = __COM_CreateGUID("{73646976-0000-0010-8000-00aa00389b71}")
Global Const $MF_TOPONODE_NOSHUTDOWN_ON_REMOVE = __COM_CreateGUID("{14932f9c-9087-4bb4-8412-5167145cbe04}")
Global Const $MF_TOPONODE_STREAMID = __COM_CreateGUID("{14932f9b-9087-4bb4-8412-5167145cbe04}")

Global Const $sIID_IMFStreamDescriptor = "{56c03d9c-9dbb-45f5-ab4b-d80f47c05938}"
Global Const $tag_IMFStreamDescriptor = $tag_IMFAttributes & _
  "GetStreamIdentifier hresult(ptr*);" & _
  "GetMediaTypeHandler hresult(ptr*);"

Global Const $sIID_IMFMediaTypeHandler = "{e93dcf6c-4b07-4e1e-8123-aa16ed6eadf5}"
Global Const $tag_IMFMediaTypeHandler = _
  "IsMediaTypeSupported hresult();" & _
  "GetMediaTypeCount hresult();" & _
  "GetMediaTypeByIndex hresult();" & _
  "SetCurrentMediaType hresult();" & _
  "GetCurrentMediaType hresult();" & _
  "GetMajorType hresult(struct*);"

Local $pSourceNode, $oSourceNode, $pIMFMediaTypeHandler, $oIMFMediaTypeHandler, $pIMFActivate
Local $pOutputNode, $oOutputNode, $tGUID = DllStructCreate($tagGUID)

For $i = 0 To $iCount - 1
  $oIMFPresentationDescriptor.GetStreamDescriptorByIndex($i, $bSelect, $pIMFStreamDescriptor)
  $oIMFStreamDescriptor = ObjCreateInterface($pIMFStreamDescriptor, $sIID_IMFStreamDescriptor, $tag_IMFStreamDescriptor)
  ConsoleWrite("oIMFStreamDescriptor " & IsObj($oIMFStreamDescriptor) & @CRLF)
  If $bSelect Then
    ; Add a source node for this stream.
    $aCall = DllCall("Mf.dll", "long", "MFCreateTopologyNode", "dword", $MF_TOPOLOGY_SOURCESTREAM_NODE, "ptr*", 0)
    $pSourceNode = $aCall[2]
    $oSourceNode = ObjCreateInterface($pSourceNode, $sIID_IMFTopologyNode, $tag_IMFTopologyNode)
    ConsoleWrite("oSourceNode " & IsObj($oSourceNode) & @CRLF)
    $oSourceNode.SetUnknown($MF_TOPONODE_SOURCE, $pMediaSource)
    $oSourceNode.SetUnknown($MF_TOPONODE_PRESENTATION_DESCRIPTOR, $pIMFPresentationDescriptor)
    $oSourceNode.SetUnknown($MF_TOPONODE_STREAM_DESCRIPTOR, $pIMFStreamDescriptor)
    $oIMFTopology.AddNode($pSourceNode)

    ; Create the output node for the renderer.

    $oIMFStreamDescriptor.GetMediaTypeHandler($pIMFMediaTypeHandler)
    $oIMFMediaTypeHandler = ObjCreateInterface($pIMFMediaTypeHandler, $sIID_IMFMediaTypeHandler, $tag_IMFMediaTypeHandler)
    ConsoleWrite("oIMFMediaTypeHandler " & IsObj($oIMFMediaTypeHandler) & @CRLF)
    $oIMFMediaTypeHandler.GetMajorType($tGUID)
    If __COM_ReadGUIDAt(DllStructGetPtr($tGUID)) =  __COM_ReadGUIDAt(DllStructGetPtr($MFMediaType_Audio)) Then
      ConsoleWrite("=== audio ===" & @CRLF)
      $aCall = DllCall("Mf.dll", "long", "MFCreateAudioRendererActivate", "ptr*", 0)
      $pIMFActivate = $aCall[1]
    ElseIf __COM_ReadGUIDAt(DllStructGetPtr($tGUID)) =  __COM_ReadGUIDAt(DllStructGetPtr($MFMediaType_Video)) Then
      ConsoleWrite("=== video ===" & @CRLF)
      $aCall = DllCall("Mf.dll", "long", "MFCreateVideoRendererActivate", "hwnd", $hWnd, "ptr*", 0)
      $pIMFActivate = $aCall[2]
    EndIf

    $aCall = DllCall("Mf.dll", "long", "MFCreateTopologyNode", "dword", $MF_TOPOLOGY_OUTPUT_NODE, "ptr*", 0)
    $pOutputNode = $aCall[2]
    $oOutputNode = ObjCreateInterface($pOutputNode, $sIID_IMFTopologyNode, $tag_IMFTopologyNode)
    ConsoleWrite("oOutputNode " & IsObj($oOutputNode) & @CRLF)
    $oOutputNode.SetObject($pIMFActivate)
    $oIMFTopology.AddNode($pOutputNode)
    $oOutputNode.SetUINT32($MF_TOPONODE_STREAMID, 0)
    $oOutputNode.SetUINT32($MF_TOPONODE_NOSHUTDOWN_ON_REMOVE, True)

    ; Connect the source node to the output node.
    $iHresult = $oSourceNode.ConnectOutput(0, $pOutputNode, 0)
    ConsoleWrite("SourceNode.ConnectOutput " & $iHresult & @CRLF)
  EndIf
Next

GUISetState(@SW_SHOW, $hWnd)

$iHresult = $oIMFMediaSession.SetTopology(0, $pIMFTopology)
ConsoleWrite("IMFMediaSession.SetTopology " & $iHresult & @CRLF)
$tGUID = __COM_CreateGUID()
Local $tVtPropEmpty = DllStructCreate("align 2;ushort vt;word Pad[3]")
DllStructSetData($tVtPropEmpty, "vt", 0)
$iHResult = $oIMFMediaSession.Start($tGUID, $tVtPropEmpty)

While True
  Switch GUIGetMsg()
    Case $GUI_EVENT_CLOSE
      ExitLoop
  EndSwitch
WEnd

$iHresult = $oIMFMediaSession.Close()
ConsoleWrite("IMFMediaSession.Close " & $iHresult & @CRLF)
Sleep(1000)

$iHresult = $oIMFMediaSource.Shutdown()
ConsoleWrite("IMFMediaSource.Shutdown " & $iHresult & @CRLF)
$iHresult = $oIMFMediaSession.Shutdown()
ConsoleWrite("IMFMediaSession.Shutdown " & $iHresult & @CRLF)
$aCall = DllCall("Mfplat.dll", "long", "MFShutdown")

; ===============================================================

Func __COM_CreateGUID($sGUID = "{00000000-0000-0000-0000-000000000000}", $pAddress = 0)
  Local $tGUID = ($pAddress And IsPtr($pAddress)) ? DllStructCreate($tagGUID, $pAddress) : DllStructCreate($tagGUID)
  Local $aGUID = StringSplit(StringRegExpReplace($sGUID, "[{}]", ""), "-", 2)
  If UBound($aGUID) <> 5 Then Return SetError(1, 0, False)
  DllStructSetData($tGUID, 1, Dec($aGUID[0]))
  DllStructSetData($tGUID, 2, Dec($aGUID[1]))
  DllStructSetData($tGUID, 3, Dec($aGUID[2]))
  DllStructSetData($tGUID, 4, Binary("0x" & $aGUID[3] & $aGUID[4]))
  Return $tGUID
EndFunc   ;==>__COM_CreateGUID

Func __COM_ReadGUIDAt($pGUID)
  Local $tGUID, $sGUID
  If (Not $pGUID) Or (Not IsPtr($pGUID)) Then Return SetError(1, 0, "")
  $tGUID = DllStructCreate($tagGUID, $pGUID)
  $sGUID = StringFormat("{%s-%s-%s-%s-%s}", _
      Hex(DllStructGetData($tGUID, 1), 8), _
      Hex(DllStructGetData($tGUID, 2), 4), _
      Hex(DllStructGetData($tGUID, 3), 4), _
      StringMid(DllStructGetData($tGUID, 4), 3, 4), _
      StringMid(DllStructGetData($tGUID, 4), 7, 12))
  Return $sGUID
EndFunc   ;==>__COM_ReadGUIDAt

ps. it is very linear, but later code is structured as it should be (see solution).

• taking part of an array as a new array
• adding element(s) at the start or middle of the array

In general array manipulation requires a loop, not a fast solution in AutoIt.

I'm thinking using IDispatch to handle variable transfer between normal variables and the raw variant pointers.

And fasm to do the array manipulation, importing the OleAut32 functions for variant manipulation.

I expect this solution to be fast, and only require AutoIt and a fasm DLL, to work.

My biggest issue currently is my lack of experience with ASM. I could try to throw something together, but would prefer help from someone, who actually knows what they are doing  

Any feedback on this idea is appreciated

thank you in advance for looking at the little project and for thinking about supporting it (me) 😀 .

Introduction
I have a small AutoIt + SQLite GitHub project (sqlite-showcase). This serves at 1️⃣. glance to demonstrate how to use SQLite using concrete examples. If questions arise in the English or German forum about SQLite, I can provide direct assistance using the project and its example data. As 2️⃣. perspective, this project is intended as a module for a subsequent project that deals with something more than "just" AutoIt + SQLite - but more on that another time.

I deliberately refrain from writing and explaining too many details here, because it is important to me, among other things, that the explanation on GitHub, in the form of a README file, can be handled or whether I need to make improvements there.

Testing
So far I have been able to test the project under Windows 10 (x64), with AutoIt v3.3.16.1 and with SQLite v3.49.0. Due to the support of the german AutoIt forum member(s), I could also test with Windows 11. Now I would be very happy if someone among you (several people are welcome) 🤗 would test other system configurations. See the following table:

The test consists of the following parts:

• Read the README, understand what to do ==> If there are already problems understanding this, then I have to make improvements.
• Setting up the project (getting started) ==> Is the explanation in the README sufficient?
  • You can test it on Windows 10 x86? Then please, great.
  • Do you have an old version of AutoIt that you can test with? That's exactly what I need ==> Thanks.
  • You want to try a different SQLite version? Why not, I appreciate it.
• Are the few SQLite functions running correctly or are there any errors? They shouldn't, but if they do, please let me know.

Preconditions
You don't need Git or GitHub, although Git is an advantage. A simple download of the project (zip) is completely sufficient (see README).
Just a little time, curiosity, interest in learning something new or putting my approach to the test 😅 .

🔥 CHANGELOG can be found here.

---------------------------------

Thank you very much for your interest and for your support. If you have any questions, please let me know. Thanks.

Best regards
Sven

Update: Testing complete.

I was thinking about how I decide to learn a new programming language. I mean, apart of professional requirements, there are some criteria for how I (and also some of my colleagues) choose a new technology or programming language. To get a good overview about how the language is written, how the syntax looks like and fits this my interests and expectations, I use cheat sheets for the specific programming language, a technology or methodology.

Also for experienced programmers who want to switch a language or as an addition, it could be helpful to understand some basics, syntax etc.

• Is there any cheat sheet for AutoIt? I didn't find any.
• Do we need it as a community or at least would it be helpful?
• Would there be some of you supporting the idea of creating one?
• Do some of you know about templates that could be used (out of the box)?

In case you are not familiar with the topic¹ and you do not know what I am talking about, please simple do a google search for "cheat sheet programming languages".

💡 There are hundreds of them, but non of these are for the AutoIt language². To spread this wonderful language to more people in the world, to support the accessibility, it should be a "must have" (among other things).

I plan to build one => in best case as a community project with several of yours.
Who wants to join?

Best regards
Sven

¹ A cheat sheet is a quick look-up reference chart or set of simple, brief instructions for accomplishing a specific task.
² It does not matter whether it's a PDF or a image in the forum which is well linked and present (next to the help) or a website.

📅 Update 2023-02-21:

AutoIt (en) Cheat Sheet

• 🔗 AutoIt (en) Cheat Sheet as website on cheatography (a website which is made to create and publish cheat sheets by the help of templates)
• 🔗 AutoIt (en) Cheat Sheet as PDF (generated by cheatography)
  • 🔗 Alternative Link to the PDF

I have been working on an enhancement to the WebDriver UDF that will make _WD_ExecuteCDPCommand compatible with all major browsers instead of Chrome only. This involves using WebSockets to pass commands back and forth to the browser.

Attached to this post are two files --

• winhttp_websocket.au3 -- This is a modified version of code originally posted to the forum by @FireFox.
• genericcdp.au3 -- This contains the enhanced version of _WD_ExecuteCDPCommand (original version by @TheDcoder) and a new function named _WD_GetCDPSettings

You can run genericcdp.au3 for a brief example of how the new functionality works. Comment / uncomment the appropriate lines near the beginning to control while browser gets tested.

Prerequisites

• You'll obviously need the WebDriver UDF installed and working for this code to have a chance of working correct. 🙄
• You need to be running an OS that supports WebSockets natively (ie: Windows 8 / Windows Server 2012 or newer)

Caveats
Chromium-based browsers return some unexpected status codes in response to _WinHttpWebSocketClose and _WinHttpWebSocketQueryCloseStatus, so I've included checks to ignore these.

Needs
I would appreciate it if I could get some feedback / suggestions for improvement on these proposed changes.

FWIW, I have only performed these basic CDP commands. Feel free to experiment with other CDP commands and report back on your successes / failures.

Thanks,

Dan

genericcdp.au3 winhttp_websocket.au3

My idea is to have a CSS with dark settings

/* JPM: modified to use inheritage widely
* 	em sizing to better zooming
* 	coloring similar to MSDN Web
*/

:root {
  color-scheme: dark
}

html {
    font-family:'Segoe UI','Lucida Grande',Verdana,Arial,Helvetica,sans-serif;
    font-size:.8125em
/* 13px; */
}

body {
    background-color:#111;
    color:#ddd;
    font-weight:400;
    max-width: 1080px;
    margin: 10px;
}

table {
    border-collapse:collapse;
    border-color:silver;
    border-style:solid;
    border-width:1px;
    margin-top:5px;
    width:100%
}

table.noborder {
    border-width:0
}

th {
/* font-size:.875em;  /* 14px; DOCTYPE without .dld */
    background-color:#2f2f2f; /* #ededed; */
    border-color:silver;
    border-style:solid;
    border-width:1px;
    color:#707070;
    padding:4px;
    text-align:left
}

th.new {
    width:224px
}

th.old {
    width:226px
}

th.width25 {
    width:25%
}

th.width75 {
    width:75%
}

tr {
    padding:4px
}

tr.yellow,tr.yellowbold {
    background-color:#808000 /* #ffff9C */
}

tr.Moccasin{
    background-color:#784a0e /* #FFE4B5 */
}

tr.yellowbold {
    font-weight:700
}

table td {
/* font-size:.875em;  /* 14px; DOCTYPE without .dld */
    border-color:silver;
    border-style:solid;
    border-width:1px;
    padding:4px
}

table.noborder td {
    border-width:0
}

td.center {
    text-align:center
}

td.right {
    text-align:right
}

td.sep {
    border-color:#111 silver
}

b {
    font-weight:700
}

u {
    text-decoration:underline
/* for HTML5 compatibility if needed */
}

p {
    margin:0;
    padding-bottom:5px;
    padding-top:5px
}

p.center {
    text-align:center
}

span.underline {
    text-decoration:underline
}

.funcdesc {
    font-size:1.25em
/* 20px; */
}

ul.cell {
    margin:0 0 0 25px
}

div.indent {
    margin-left:32px
}

a,a:link {
    color:#00709f
}

a:visited {
    color:#03697a
}

a:active {
    color:#2a2a2a
}

a:hover {
    color:#3390b1
}

a,a:link,a:visited,a:active {
    text-decoration:none
}

a:hover {
    text-decoration:underline
}

a.ext:link,a.ext:visited,a.ext:active {
    text-decoration:underline
}

a.codeSnippetLink:hover {
    text-decoration:underline
}

h1 {
    color:#707070;
    font-size:2.75em;
/* 36-44px; */
    font-weight:400;
    margin:0;
    padding-bottom:15px;
    padding-top:15px
}

.small {
    font-size:.875em;
/* 12-14px; */
    margin:-12px 0 -4px;
    padding-bottom:0;
    padding-top:9px
}

h2 {
    color:#db7100;
    font-size:1.5em;
/* 24px; */
    font-weight:400;
    line-height:normal;
    margin:0;
    padding-bottom:5px;
    padding-top:25px
}

h3 {
    color:#0073e6; /* navy; */
    font-size:1.0625em;
/* 17px; */
    font-weight:700;
    line-height:normal;
    margin-bottom:0;
    margin-left:5px
}

pre,.code,.codeheader,.codebox {
    font-family:"Courier New",Courier,monospace
}

.code {
    white-space:nowrap
}

.codeheader {
    background-color:#565656; /* #ffa; */
    border-bottom:1px solid #ffa; /* #aaa; */
    border-left:1px solid #ffa;
    border-right:1px solid #ffa;
    border-top:1px solid #ffa;
    padding:16px;
    white-space:normal
}

.codebox {
    border-bottom:1px solid #aaa;
    border-left:1px solid #aaa;
    border-right:1px solid #aaa;
    border-top:1px solid #aaa;
    color:#465584;
    overflow-x:auto;
    padding:8px 8px 16px;
    margin-top:5px;
    white-space:nowrap;
    width:99%
}

.S0 {
    color:#CaCaCa /* #2a2a2a */
}

.S1 {
    color:#609F60;
    font-style:italic
}

.S2 {
    color:#609F60; /* green; */
    font-style:italic
}

.S3 {
    color:#C0FFFF /* blue */
}

.S4 {
    color:#8080FF /* #000090 */
}

.S5 {
    color:#C080C0 /* blue */
}

.S6 {
    color:olive
}

.S7 {
    color:#F0E090 /* red */
}

.S8 {
    color:#FF8000
}

.S9 {
    color:#D0D0D0 /* #2a2a2a */
}

.S10 {
    color:gray
}

.S11 {
    color:#8996A7 /* olive */
}

.S12 {
    color:#dc143c
}

.S13 {
    background-color:#DDE8F0;
    color:red
}

.S14 {
    color:#993399 /* #939 */
}

.S15 {
    color:#0080ff
}

.bottom {
    padding-bottom:0;
    margin-bottom:0
}

.experimental {
    background-color:#ffffe0;
    border:solid;
    border-color:red;
    font-size:1.5em;
/* 24px; */
    font-weight:700;
    margin:12px;
    padding:4px
}

.specialnote {
    background-color:#fffffa;
    border:solid;
    border-color:blue;
    font-size:1.5em;
/* 24px; */
    font-weight:500;
    padding:4px
}

img.logo_v3 {
    /* box-shadow:5px 5px 20px #aaa */
}

.noPageBreak {
    page-break-inside:avoid
}

/* adapted from MSDN Web for example code open/copy actions */
.codeSnippetContainer {
    min-width:260px;
    margin:0;
    padding:0
}

.codeSnippetContainerTabs {
    font-size:.8333em;
/* 13.33px 10pt!important; */
    height:20px;
/* 22px; */
    position:relative;
    vertical-align:middle;
    z-index:1
}

.codeSnippetContainerTab {
/* background:none repeat scroll 0 0 #eff5ff; */
    border-bottom:2px solid #d0d2d2;
    border-top:1px solid #bbb;
    border-left:1px solid #929292;
    float:left;
    height:20px;
/* 19px; */
    padding:0 4px;
/* 0 8px; */
    width:auto;
    overflow:hidden;
    position:relative;
    font-weight:400
}

/* MSDN not used
* .codeSnippetContainerTabActive
* {
* 	height:21px;
* 	background:none repeat scroll 0 0 #111;
* 	border-left:1px solid #bbb;
* 	border-bottom:none;
* }
* 
* .codeSnippetContainerTabFirst
* {
* 	border-radius:4px 0 0 0;
* 	padding:0 8px 0 6px;
* }
* 
* .codeSnippetContainerTabLast
* {
* 	border-right:1px solid #bbb;
* 	border-radius:0 4px 0 0;
* 	padding:0 6px 0 8px;
* }
*/
.codeSnippetContainerTabSingle {
    border:none;
    color:#00709f;
/* #e66a38; */
    vertical-align:baseline;
    top:10px;
/* 8px; */
    left:12px;
/* 7px; */
    position:relative;
    background-color:#111
}

.codeSnippetContainerTabSingle a {
    color:#e66a38
/* !important; */
}

.codeSnippetContainerTab a,.codeSnippetContainerTab a:link,.codeSnippetContainerTab a:visited,.codeSnippetContainerTab a:active {
    color:#1364c4;
    text-decoration:none
}

/* MSDN not used
* .codeSnippetContainerTabActive a,.codeSnippetContainerTabActive a:link,.codeSnippetContainerTabActive a:visited,.codeSnippetContainerTabActive a:active
* {
* 	color:#e66a38;
* 	text-decoration:none;
* 	position:relative;
* }
* 
* .codeSnippetContainerTabPhantom a,.codeSnippetContainerTabPhantom a:link,.codeSnippetContainerTabPhantom a:visited,.codeSnippetContainerTabPhantom a:active
* {
* 	color:#c2c2c2;
* 	text-decoration:none;
* 	position:relative;
* }
* 
* .codeSnippetContainerTabPhantom a:link,.codeSnippetContainerTabPhantom a:visited,.codeSnippetContainerTabPhantom a:active
* {
* 	color:#707070;
* 	text-decoration:none;
* 	position:relative;
* }
*/
.codeSnippetContainerTab a:hover {
    color:#e66a38;
    position:relative
}

/* MSDN not used
* .codeSnippetContainerTabPhantom a:hover
* {
* 	color:#c2c2c2;
* 	position:relative;
* }
*/
.codeSnippetContainerCodeContainer {
    border-bottom:3px solid #5e5e5e; /* #e5e5e5; */
    border-left:3px solid #5e5e5e;
/* 1px */
    border-right:3px solid #5e5e5e;
/* 1px */
    clear:both;
    margin-bottom:0;
/* 12px; */
    position:relative;
    top:-3px
}

.codeSnippetToolBar {
    border-left:0 solid #5e5e5e;
/* 1px */
    border-right:0 solid #5e5e5e;
/* 3px */
    border-top:3px solid #5e5e5e;
    height:auto;
    width:auto
}

div.codeSnippetToolBarText {
    float:right;
    top:-12px;
/* -8px; */
    position:relative;
    background-color:#111;
    width:auto;
    padding-left:4px;
    padding-right:4px;
    height:0;
    vertical-align:top
}

div.codeSnippetToolBarText>a:link,div.codeSnippetToolBarText>a:visited,div.codeSnippetToolBarText>a:active {
/* display:none; */
    margin-left:5px;
    margin-right:5px;
/* font-size:100%; /* 83.33%; /* 10pt */
/* font-style:400!important; */
/* color:#1364c4; */
    text-decoration:none;
    background-color:#111;
    padding-left:4px;
    padding-right:4px
}

div.codeSnippetToolBarText>a:hover {
    text-decoration:underline
}

.codeSnippetContainerCode {
    margin-top:14px;
/* 0; */
    padding:5px 10px;
/* 9px 21px; */
    width:auto
}

.codeSnippetContainerCode div {
    padding:0;
    margin:0
}

.codeSnippetContainerCode pre {
    padding-left:5px;
/* 5px; */
    margin:0;
/*word-break:break-all;*/
    font-style:normal;
    font-weight:400;
    overflow:auto;
    word-wrap:normal
}

#hhctrl {
    vertical-align:middle
}

#hhctrl-bottom {
    vertical-align:bottom
}

.codeSnippetContainerTab object {
    cursor:pointer;
    text-decoration:underline
}

.valign-top {
    vertical-align:text-top
}

as to see something more like: ( and this is just my browser over the help file to present the idea )

the issues are that -I'm not color blind but- coloring is something am not good at.

If I ask to get this done, it has to be definitive, as in "use this CSS for an alt. coloring", but if tomorrow I'm like, let's change this a little bit, today I woke up with the idea of pastels, I'm gonna get kicked in ... the code. 

If you need to get the files from the CHM to have a go at it run hh.exe -decompile C:\SomePath\Folder AutoIt.chm to get to edit and test the colors ( in html\css\default.css ).

Am asking for collaboration to have acceptable colors, given that my coloring skill leave much to be desired and in consensus we all can come to a globally acceptable coloring scheme. Post your CSS if you made one.

Thanks.

easy like Autoit but power like c and c++ and multiplatform , I wanted to suggest if possible a potential merger with AutoIt or a fork because it could allow for the integration of AutoIt or whatever may come out of it (a combination like AutoRing or a separate project named Ringo). I have already created some classes in the AutoIt style

func GuiCtrlComboBox(Refer,X,Y,Xw,Yh,alist,Tooltip){
        new QComboBox(Refer) {
                        settooltip(Tooltip)
                        setGeometry(X,Y,Xw,Yh)
                        oFont = new qfont("",0,0,0)
			oFont.fromstring("Arial,8,-1,5,50,0,0,0,0,0,Regular")
			setfont(oFont)
			oFont.delete()
                        for x in aList additem(x,0) next
                }
}

 GUICtrlCreateButton(pageCO1,5,60,51,25,"BUYmk","pWork()","Green","")
                         GUICtrlCreateButton(pageCO1,163,60,51,25,"SELLmk","pWork()","Red","")
                         GUICtrlCreateButton(pageCO1,5,90,51,25,"BUYlmt","pWork()","Green","")
                         GUICtrlCreateButton(pageCO1,163,90,51,25,"SELLlmt","pWork()","Red","")
                         sBuyLimtImput=GUICtrlCreateInput(pageCO1,5,120,90,21,"")
                         sSellLimtImput=GUICtrlCreateInput(pageCO1,124,120,90,21,"")
                         GUICtrlCreateButton(pageCO1,5,145,75,25,"BUYStplmt","pWork()","Green","")
                         GUICtrlCreateButton(pageCO1,140,145,75,25,"SELLStplmt","pWork()","Red","")
                         sBuy4STPImput=GUICtrlCreateInput(pageCO1,5,175,90,21,"")
                         sBuy4LimtImput=GUICtrlCreateInput(pageCO1,5,195,90,21,"")
                         sSell4STPImput=GUICtrlCreateInput(pageCO1,124,175,90,21,"")
                         sSell4LimtImput=GUICtrlCreateInput(pageCO1,124,195,90,21,"")
                         GUICtrlCreateButton(pageCO1,5,220,75,25,"BUYOCO","pWork()","Green","")
                         GUICtrlCreateButton(pageCO1,140,220,75,25,"SELLOCO","pWork()","Red","")
                         sBuyOCOSTPImput=GUICtrlCreateInput(pageCO1,5,250,90,21,"")
                         sBuyLimtOCOImput=GUICtrlCreateInput(pageCO1,5,270,90,21,"")

In my opinion, the weaknesses of Ring are: limited documentation and support only through the mailing list, making it challenging to retrieve discussions that could be beneficial for growth. It would be great to see a merger or fork to create a unified community.

Ring is a dynamic programming language designed to provide a simple and versatile development environment. Here are some of its strengths:

1. Clean and clear syntax: Ring is designed with a clear and readable syntax, making it accessible even to those new to programming. This contributes to easy code understanding and rapid development.

2. Multi-paradigm: Ring supports multiple programming paradigms, including imperative, functional, and object-oriented programming. This allows developers to use programming styles that best suit their project needs.

3. Dynamic typing: Ring is a dynamically typed language, meaning that the type of a variable is resolved at runtime. This provides greater flexibility during development, allowing for more concise and adaptable code.

4. Portability: Ring is designed to be highly portable and can run on various platforms, including Windows, Linux, and macOS,Android without requiring significant modifications to the source code.

5. Integrated libraries: Ring includes a set of integrated libraries to facilitate application development. These libraries cover a wide range of functionalities, from string handling to file manipulation, making it easier to create complex software.

I know about several of us do have AutoIt projects on GitHub.
In this hopefully growing collection I want to list forum members and their GitHub projects (AutoIt based).

Why?
One use case could be the contribution to some of their projects.
Assume that AutoIt projects are not that wide spreaded or supported in terms of contribution (participation), as JavaScript projects for example.

• Wouldn't it be nice to get more contribution on your project?
• Wouldn't it be nice to work on bigger projects in a community?

I personally would love to 😀 .

Disclaimer:
As the GitHub profiles (and repositories), I will list here, are public and your profiles either findable by your signature, your "About Me" page or by a simple Google or GitHub search 🔍 , I see no restriction to collect these kind of information and post it here. In case you don't agree with this visualisation and you don't want to be listet here, please let me know and I will remove that entry as soon as possible 🤝 . I really hope that fits your feeling about it.

Collection (in progress):

@Forum username » GitHub username » Link to the GitHub projects (filtered by language=autoit)

• @Alan72104 » Alan72104 » Projects
• @alexanr1 » alexanr1 » Projects
• @AspirinJunkie » Sylvan86 » Projects
• @Centrally » ellysh » Projects
• @Danp2 » Danp2 » Projects
• @Danyfirex » DanysysTeam » Projects
• @DonChunior » DonChunior » Projects
• @ergo » seizu » Projects
• @genius257 » genius257 » Projects
• @J2TeaM » J2TEAM » Projects
• @James » jbrooksuk » Projects
• @Jefrey » jesobreira » Projects
• @jvanegmond » jvanegmond » Projects
• @kurtykurtyboy » KurtisLiggett » Projects
• @lamnhan066 » lamnhan066 » Projects
• @LinkOut » xLinkOut » Projects
• @LoganCH » loganch » Projects
• @Mat » MattDiesel » Projects
• @Mateocedillo » rmcpantoja » Projects
• @matwachich » matwachich » Projects
• @mLipok » mlipok » Projects
• @MrKm » MurageKabui » Projects
• @NHD » nomi-san » Projects
• @oHenry » htejera » Projects
• @OvisMaximus » OvisMaximus » Projects
• @philpw99 » philpw99 » Projects
• @rcmaehl » rcmaehl » Projects
• @Rurorita » OfficialLambdax » Projects
• @rynow » 4ern » Projects
• @scintilla4evr » scidsgn » Projects
• @seadoggie01 » seadoggie01 » Projects
• @seangriffin » seanhaydongriffin » Projects
• @smbape » smbape » Projects
• @SOLVE-SMART » Sven-Seyfert » Projects
• @Stilgar » THWillert » Projects
• @Surya » thesunRider » Projects
• @tarretarretarre » tarreislam » Projects
• @TheDcoder » TheDcoder » Projects
• @TheSaint » Twombs » Projects
• @trancexx » dragana-r » Projects
• @vietanhdev » vietanhdev » Projects

Σ = 41

I would love to see the list growing and I am very excited about a possibly upcoming behavior and improvement change, regarding AutoIt on GitHub 😊 .
💡 Please help me to increase the list. Either by your GitHub link (profile) or through a link from a member you know.

Best regards
Sven

________________
Stay innovative!

Donwload Link:

https://www.autoitscript.com/forum/files/file/512-atcmdau3-udf/

Saludos

and
https://github.com/microsoft/WinAppDriver

AnyBody know how to use this with AutoIt ?

see how it works here:

YouTube preview