xdo VS NaturalEdgePan

An example with xdo:

I might have understood your question wrong, if you want to close the GUI window after staring the app you'd want to take a look at xdo. I'd still give it a little bit of time after starting it to be ready and then use something like:

xdo (by baskerville, bspwm's creator);

The focusonnetactive patch replaces dwm's default behavior by removing the urgency bit to allow for focusing on the client sending the _NET_ACTIVE_WINDOW message instead. This is the preferred behavior if you use tools like xdo to perform actions on windows, for example:

AutoIt is also great especially for quickly prototyping GUIs.

I recently built a proof-of-concept for a modernized method of interacting with RTS cameras[0], which unfortunately could not be achieved with frameworks like SDL due to their abstraction obscuring some of the native OS functions needed to create my idea.

Using AutoIt lets me basically just treat it as a minimal-boilerplate sandbox to make DllCalls. This also means that I could directly listen as well as post raw device messages. For example, I implemented an inertia-based cursor script that basically lets you use your homerow vim keys like it's a trackball[1], which I now use everyday whenever I'm not with my ThinkPad.

[0] https://github.com/EsportToys/NaturalEdgePan

I came across this very interesting bit of history while looking for an image to illustrate my RTS camera control concept[0] as an analogy.

It's interesting how a lot of the wartime "computational drudgery" frequently employ women, the perception of which shifted to becoming a more men-dominated employment after the war.

It would be lovely to hear interesting perspectives from people here on what other tidbits you know of about little-known roles and the social climate during the war, or your insights on how things came to be the way they are during and after the war.

[0] https://github.com/EsportToys/NaturalEdgePan#figure-2-this-w...

So I made this prototype, to show how I think new-players can be encouraged to use unlocked camera more effectively -- I think the main friction is less about traditional edge-panning being inefficient, and more about it being accident-prone: players acquiring mouse precision at the same time as learning the game finds themselve accidentally panning the camera when the cursor is close to the edge, so early on they develop a bad habit of leaving a wide space for where you are clicking rather than developing the motor control to kite with the cursor close to the screen-edge and hero.

A playable demo downloadable from GitHub

You can feel it out in the playable demo here!

NaturalEdgePan