Apr-24-2021, 10:50 PM
Actually when I click the initial open next window the spawned window does not become active until I click open next window.
Which is the issue I was noticing when I tried to use -topmost true option.
The kicker is I am trying to ensure the window spawned is automatically active and at the top so that it will accept keyboard input.
The question I have to wonder is this a Windows 10 problem, or is it a tkinter problem, or is it a python problem.
The example is rather inspired.
So on my main script I launch it. Splash screen does its thing then it goes to the select screen as I call it. I then hit spacebar to go to the fire screen as I call it. I have to click the fire screen to make it active before I can hit key, "f" to get the firing logic to start applying.
The majority of users are going to be windows users, some Linux, and many Raspbian users along with a few macOS users. So I think this quirk is something I might want to address to keep the script more user friendly.
The flash software I am replacing did not have this issue so I am more leaning that it is an issue with the way I am coding things or it could be the way windows desktop manager is misbehaving or behaving depending upon ones point of view...
Which is the issue I was noticing when I tried to use -topmost true option.
The kicker is I am trying to ensure the window spawned is automatically active and at the top so that it will accept keyboard input.
The question I have to wonder is this a Windows 10 problem, or is it a tkinter problem, or is it a python problem.
The example is rather inspired.
So on my main script I launch it. Splash screen does its thing then it goes to the select screen as I call it. I then hit spacebar to go to the fire screen as I call it. I have to click the fire screen to make it active before I can hit key, "f" to get the firing logic to start applying.
The majority of users are going to be windows users, some Linux, and many Raspbian users along with a few macOS users. So I think this quirk is something I might want to address to keep the script more user friendly.
The flash software I am replacing did not have this issue so I am more leaning that it is an issue with the way I am coding things or it could be the way windows desktop manager is misbehaving or behaving depending upon ones point of view...
