Question about something I am trying with dxNothing windows

So I made a minimap that shows all 4 of my accounts minimaps in a grid. Since you can't use a viewer on a source in the same window, I did this with a dxNothing window. This works great when set to always on top, but then the dxnothing is blocking other game elements at times.

Is there a way to toggle the always on top state for a dxNothing window?

I see Window State and Style actions when I try to make new Mapped Keys but I am not exactly sure how to use them and so far my efforts haven't produced any results. I basically want to be able to set it to always on top when I am gaming most of the time and then when I open UI elements like game menus, inventory, etc I want to be able to take off the always on top state and push it to the background so it isn't blocking other UI elements.

Is this even possible?

[MiRai]

From what I understand, you should be using the Foreground (and always on top) options if you want to switch another Region to be on top of your dxN region. Then reverse that when you want to put the dxN region back on top.

Thanks MiRai, the little nugget helped point me in the proper direciton. I am on my way to the correct functionality I was looking for.

Right now I have created two new Mapped Keys.

The first is the key to toggle the dxnothing minimap off and on and its actions look like this:

Change Foreground window style -> self
Change Background window style -> 6
Switch window to Foreground (Full) -> self
Switch window to Background (Full) -> 6
Change Foreground window style -> self (this always turns off always on top for the current window)

The above seems to set the styles, try to switch the windows even though they are currently in foreground and background anyway, and then resets the current window to not have always on top. If I plan to use it as a true toggle that last line might need to change. Currently it does seem to cycle properly.

The second one uses the same commands mostly but instead of any toggling it just sets all game windows to not always be on top, sets the dxnothing to always on top and then does the window switches to update everything. This results in basically setting it to the default I normally run in anyway. This works pretty well. I may need to run through some flowcharts for all the possible ways I want to show/hide the dxnothing just to make sure I don't get windows stuck in states or settings I don't want. So far though I think I have learned enough about how to make it do what I want that I can figure the rest out.

[bob]

You might have a few issues if these actions are all in the same step.

Actions in the same Step are all run at effectively the same time, in order top to bottom, but there are caveats (this is based on my understanding so may not be right; and when I said "effectively the same time" I mean if you had several Keystroke actions, it's like pressing all those keys on the keyboard at the same time).

1. All actions to "self" will run before any other actions in the current step. This is because there is no work in determining which window they go to.
2. All actions to any other window, need to be processed to determine where they go, and whether it will be accepted, so they will happen after any sent to self (and yes this is a repeat of the above but around the other way).
3. When an action is sent to a window other than self, then that sending is asynchronous, so it is possible that they do not arrive in the order specified.
4. If you need a list of actions to be processed in a specific order but in other windows, you can fake it by calling Do Mapped Key Actions on self and those called Mapped Keys have the actions that may or may not send to other windows, so you essentially end up with a mapped key that calls other mapped keys.

______________________________________________________________________________________________________________________________________________________________
My deranged ramblings are subject to be changed frequently, and completely contradicted by people who actually know the answer to your question.

Hmm, didn't think about that. So far I don't seem to be having any issues and yes they are all in one step. I may just be getting lucky though.

I am already calling other mapped keys from mapped keys for other purposes, so if I have any issues with this function I will look into that. Thanks for the tip!