Gui stuff#187
Conversation
click stuff, beginning of
added some clicking stuff back after merge from upstream daddy
Unknown6656
left a comment
There was a problem hiding this comment.
I know that your branch is currently work-in-progress, but I wanted to warn you, that targeting net8.0-windows will NOT be possible, as this project needs to run under Linux and MacOS as well.
| <PropertyGroup> | ||
| <OutputType>Exe</OutputType> | ||
| <TargetFramework>net8.0</TargetFramework> | ||
| <TargetFramework>net8.0-windows</TargetFramework> |
There was a problem hiding this comment.
I unfortunately cannot permit binding to netX.X-windows, as the project would not be runnable on MacOS or Linux (which is the ultimate aim of this project).
Please change it back to net8,0. If you need windows-specific functions, use direct P/Invoke calls to the Windows Libraries (and if possible, provide also POSIX-compatible alternative code for non-Windows operating systems).
| <TargetFramework>net8.0-windows</TargetFramework> | ||
| <EnablePreviewFeatures>true</EnablePreviewFeatures> | ||
| <LangVersion>preview</LangVersion> | ||
| <UseWindowsForms>true</UseWindowsForms> |
There was a problem hiding this comment.
same rule applies as to the comment above.
| using System.Linq; | ||
| using System.Text; | ||
| using System; | ||
| using System.Drawing; |
There was a problem hiding this comment.
Afaik not possible under Linux and MacOS, correct me if I'm wrong.
| using Unknown6656.AutoIt3.Extensibility; | ||
| using Unknown6656.AutoIt3.Runtime.Native; | ||
| using Unknown6656.AutoIt3.Runtime; | ||
| using System.Drawing; |
There was a problem hiding this comment.
same potential issue as mentioned above.
# starting to add some windows specific stuff
Enables FileOpenDialog etc. that's already in WindowsSpecificFunctions, and adds MouseGetPos, MouseClick, etc. Only absolute positions so far, relative not yet handled. Would love to see some of the GUI automation stuff in here, this is just a start, to learn what's going on. If you take this and run with it, cool! Otherwise I may add some more as I run into use cases