Ahh. I mistook your form letter for a bot message because, when [Mod] Synchunk sent it, I asked if he was a bot and never got a response.
As for fixing the problem, Scott Zeid went into quite a bit of detail on how simple it is.
Yes, Mr. Bot.
It's still a problem and waiting for me to go away will not magically make it possible to write a rule which reliably matches Minecraft windows regardless of their version.
_OB_APP_TYPE(UTF8_STRING) = "normal"
_OB_APP_TITLE(UTF8_STRING) = "Unnamed Window"
_OB_APP_CLASS(UTF8_STRING) = "Minecraft 1.8.1-pre3"
_OB_APP_NAME(UTF8_STRING) = "Minecraft 1.8.1-pre3"
_OB_APP_ROLE(UTF8_STRING) =
I have a question of my own. Given that you didn't answer my question and there seems to be little interest in fixing this bug, are you just a bot designed to keep the number of open bugs down by burdening users who complain in the hope that the less stubborn ones will shut up and go away?
Also, yes, it still is a problem.
_OB_APP_TYPE(UTF8_STRING) = "normal"
_OB_APP_TITLE(UTF8_STRING) = "Unnamed Window"
_OB_APP_CLASS(UTF8_STRING) = "Minecraft 14w21b"
_OB_APP_NAME(UTF8_STRING) = "Minecraft 14w21b"
_OB_APP_ROLE(UTF8_STRING) =
Do I amend this bug or open a new one if the WM class and name are now set but aren't usable because they change with every minor version?
I still can't set a reliable window management rule when my only tool is exact-string matching against one or more of these values. (And the same problem would apply to any kind of macro harness or key mapper which binds profiles to window classes.)
_OB_APP_TYPE(UTF8_STRING) = "normal"
_OB_APP_TITLE(UTF8_STRING) = "Unnamed Window"
_OB_APP_CLASS(UTF8_STRING) = "Minecraft 1.7.5"
_OB_APP_NAME(UTF8_STRING) = "Minecraft 1.7.5"
_OB_APP_ROLE(UTF8_STRING) =
My suggestion would be to set the window class to "Minecraft" while leaving the window name at its current value so that users have a choice to match either all Minecraft versions or just a specific one.
I suspected as such, but I'll take any opportunity I can get to draw attention to how, were I a developer already versed in the project, Scott Zeid provided enough information that I could probably apply and test the fix in 5 minutes.
Maybe someday it'll actually trickle through to the devs.