Idea initally by Homes32 here
Sadly, previous syntax and codes had troubles:
* not compatible to all active wb versions, working slow, and does not give expected result on some cases.
a better (au3) implementation asked, but not responded.....
Checking api syntax deeply on weekend, I had more and more hesitations for future......
In the end, api syntax changed, and au3 implemented with great help of BlueLife
* quite fast now and giving expected results, and will not require syntax change in future.
to write or read:ChangeInterface
=>Value | State | Position
more elements can be added in future IF required
ex: Title , PosTop , PosLeft , Width , Height , ToolTip , SectionRun , ProgressShow , Size , FontSize , FontType , PositionLeft .........
Currently it seems most demanded are Value and State (State=visible or not), and to keep things simple better continue this way.
using ChangeInterface,Read , result will be %var%
If you use ChangeInterface,Read,.....,MyVariable ---> result will be %MyVariable%
I personally advice not use extensively since capi development can not hold responsibility for position,
currently wb have first 7 position stable, and rest is jumping around (requires au3 etc.),
my advice, use positions max. 7 - 8 to keep stability on your scripts, further up to you.....
a note for future developers, be carelful (currently) for radiogroup, radiobutton and CheckList
ex: reading/writing 2nd value of a checklist may require additional parameters asides Write/Read.... or read/write 3rd elements title of a radiogroup...
I believe we do not need these examples...., If someone have a looot free time a complete au3 which has all editorial features of wb can be written, and can be implemented to capi, I hope you benefit from current au3.
Use following, exagarated test package to see what can be done with ChangeInterface,
it will be quite fun and nice practice having simple examples.