taskbar | a systray shell for console application | Command Line Interface library

To display OpenGL with a Java application that uses JavaFx, I use a GLFW window that is positioned behind a transparent area of my application. This gives the illusion that OpenGL views are part of the application.

Under Windows 10, this GLFW window is visible and selectable in the taskbar, which short-circuits its enslavement by the application and makes it out of control :

I imagine that it is possible by code (I am considering in C via the JNI) to hide in the taskbar this GLFW window (whose window handle is given) but I am not sure what must be accessed in the bowels of the Windows OS.

If anyone has an idea or can guide me on which part I need to document.

I am new to python, actually new to programming too, and I am recently working on a simple project with Tkinter. In this project, I was trying to create a force attention window and I finally got the answer from this page. The main codes are as follows:

If I open Spyder via the window taskbar (i.e clicking on the search button in the lower left, typing "spyder", and clicking on the app), I can get a list of environmental variables with list(os.environ.keys())

If I then open Spyder through an Anaconda Prompt (i.e. opening an Anaconda Prompt window, typing in "spyder", and hitting enter), and do the same thing, several extra environmental variables show up.

These are the variables which show up in list(os.environ.keys()) in Spyder opened through the Anaconda Prompt, but do not appear in the Spyder instance opened through the Windows taskbar:

I am working on a p2p application and to make testing simple, I am currently using udp broadcast for the peer discovery in my local network. Each peer binds one udp socket to port 29292 of the ip address of each local network interface (discovered via GetAdaptersInfo) and each socket periodically sends a packet to the broadcast address of its network interface/local address. The sockets are set to allow port reuse (via setsockopt SO_REUSEADDR), which enables me to run multiple peers on the same local machine without any conflicts. In this case there is only a single peer on the entire network though.

This all works perfectly fine (tested with 2 peers on 1 machine and 2 peers on 2 machines) UNTIL a network interface is disconnected. When deactivacting the network adapter of either my wifi or an USB-to-LAN adapter in the windows dialog, or just plugging the usb cable of the adapter, the next call to sendto will fail with return code 10049. It doesn't matter if the other adapter is still connected, or was at the beginning, it will fail. The only thing that doesn't make it fail is deactivating wifi through the fancy win10 dialog through the taskbar, but that isn't really a surprise because that doesn't deactivate or remove the adapter itself.

I initially thought that this makes sense because when the nic is gone, how should the system route the packet. But: The fact that the packet can't reach its target has absolutely nothing to do with the address itsself being invalid (which is what the error means), so I suspect I am missing something here. I was looking for any information I could use to detect this case and distinguish it from simply trying to sendto INADDR_ANY, but I couldn't find anything. I started to log every bit of information which I suspected could have changed, but its all the same on a successfull sendto and the one that crashes (retrieved via getsockopt):

I intend to run a Linux-based container on Windows. I installed Docker 4.3.2 and 4.4.4 community editions based on WLS2 to do that. After enabling all prerequisites for windows (WSL2, Hyper-V, Containers) and installing Docker, I tried to launch the docker desktop, at first, the docker icon appears on the taskbar but after a few seconds it disappears without showing any error message.

System specification:

• OS: Windows 11 pro version 21H2 Build 22000.376
• Docker version: 4.3.2 community edition
• WSL: wsl v2

Here is the log for last try:

I have a Windows Desktop WPF application that is using the MSAL libraries to authorize a user against Azure Active Directory. It is all working, except the prompt where the user selects their account sometimes ends up behind the application (I assume when a user selects a different application in the taskbar prior completing the MSAL prompt).

I have added the WithParentActivityOrWindow option and pointed it to the main window of the application, but that doesn't attach the prompt to anything or force it in front of the application.

Is is possible to do one of the following, and if so, how?

• Force the prompt to receive focus whenever the application is the 'active' Windows application
• Embed the prompt within a WPF UserControl

For reference, the example code here is almost identical to what I'm using: https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-desktop-acquire-token-interactive?tabs=dotnet

Edit: I noticed today that Visual Studio blocks until the OAuth prompt is completed, but I'm not sure how this is accomplished or if Visual Studio is using the MSAL libraries at all.

We can SetForegroundWindow for a window.

Is there a function to make its icon blinking a number of times on taskbar ?

I have tried things like SetActiveWindow and ShowWindow, to no avail.

As we know, Microsoft choosed not to display seconds in Windows 11 system tray taskbar. Thus, I decided to create a little tool.

A simple timer and a label to show seconds next to the clock. The code I'm using is:

I currently have an Ubuntu docker container to run GUI applications called Gazebo and ROS. I am using Vcxsrv to run the GUIs on my windows host os and am able to display a GUI. However the problem is that I can only display one GUI from one bash of my running docker container at a time as I am able run my first GUI program, Gazebo, in the first docker container bash. But after I run a new bash with "docker exec -it bash" and then run another GUI program, like one called Rviz, I get the error here: