Open agzam opened 4 months ago
Currently you have _NET_WM_NAME(UTF8_STRING) = "FlowStorm debugger"
which I use with i3 wm for example.
You can customize it you start the UI with :
(fs-api/local-connect {:title "MyFlowStorm"})
Do you think it is enough or is there a reason to still prefer a JVM property to customize the class ?
The title often is not enough as some window managers customize window behavior based on the WM class. But please, don't worry about it, if I get bandwidth for this, I'll send a PR. The issue is for my own sake and for general posterity. I do sometimes go over the issues I filed in various OSS projects and see if I can provide a fix.
Great, thanks @agzam, I would appreciate a PR for it if you think it is useful.
xprop WM_CLASS
currently reportsWM_CLASS(STRING) = "java", "java"
. That makes it slightly more difficult to incorporate the app into X11 and various window manager workflows.