David Krutsko
David Krutsko
An ability to change window opacity might be nice to add to the Window class.
Currently, when you use a function like [Process::GetList](https://github.com/Robot/robot/blob/master/Source/Process.cc#L950-L1039), it opens a handle to every process before potentially adding it to the resulting list. This might compromise the security in some...
Currently, memory manipulation is implemented through reading and writing to the `/proc/mem` file. This doesn't work across all distributions and may benefit from an alternate method. One method of implementing...
X11 is great, but the windowing systems on Linux are changing. In order for certain distributions to become supported, libraries like [Wayland](//en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29) and [Mir](//en.wikipedia.org/wiki/Mir_%28software%29) will need to be used instead....
The Clipboard class does not currently support Linux. For this to be implemented on X11, a window needs to be created which will "own" the selected clipboard data. Since #2...
Likely would need to integrate with some sort of library. But an assembler for for x86 and x64 code would be a nice addition for certain situations. One example could...
Likely a huge project but not necessarily out of the scope of this library. Not sure what sort of features would be supported but it would be useful in a...
Functions like `Window::IsResizable`, `Window::Get/Set Min/Max Bounds` might be useful for rounding out the Window class.
The next step beyond process manipulation is thread manipulation. Functions such as creating, pausing, resuming, deleting and enumerating remote threads (among other functions) would be a huge help for certain...