uncle808us opened this issue on Dec 21, 2019 ยท 5 posts
an0malaus posted Sun, 22 December 2019 at 2:53 AM
You are probably seeing the initial, and ultimately failed attempt to address the problem I reported of Poser simply hiding all of its child windows when it was no longer the foreground application. Those child windows could never be seen at all when Poser was in the background (whether hidden or not). I asked that Poser behave as other Mac apps do, and simply allow those child windows to remain visible, but be backgrounded as the main window can, with other app windows appearing in front when they are the foreground app.
The implementation of this standardised macOS behaviour was not complete, with Poser's child windows neither hiding, nor receding to the background. They stubbornly remained in the foreground in front of applications which had the focus. This unfortunate attempt drew understandable complaint for not just changed, but even more unfriendly behaviour, and resulted in the feature being rolled back to the initial, mildly unhelpful behaviour.
I had requested the feature change, because I wanted to be able to transcribe python script output and prototyping code, and parameter values directly into a text editor, or terminal shell window, with the Poser child windows remaining visible. Unfortunately, this will probably never happen, now, due to the clap-back from the failed implementation attempt.
In defence of the devs, I am aware that there are many components of Poser that derive from third parties and whose support depends on those parties. Unfortunately, some of those (~10 year old) components have been deprecated/retired from active support in favour of more recent versions. The newer versions do not appear to support exactly the same functionality, which is a cause for concern, and subtle, or not so subtle, enforced feature changes in the latest releases of Poser.
Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.