ProppFrexx Won’t Close When Using a Group Container on a Second Monitor

[John2103]

I have a Group Container on the second monitor of my computer. Since yesterday, ProppFrexx has been refusing to close. However, if I remove all windows from the Group Container, ProppFrexx closes normally.

I have deleted the settings from `C:\Users\John\AppData\Roaming\radio42\ProppFrexx ONAIR\4.0\` and reconfigured everything from scratch. However, the problem persists.

As soon as I place two or more windows in a Group Container on the second monitor, ProppFrexx refuses to close.

Is there a solution to this problem?

[radio42]

I can not reproduce the issue.
Maybe there is something else broken, which I can not reproduce.

Have you tried resetting the layout, eg. by deleting the *.layout files in the ProppFrexx AppUserData folder?

Can you after such cleanup clearly reproduce the issue?
If yes, please describe exactly the steps.

[John2103]

Here is what I did. I deleted all the layout files for the user.

I then created a Group Container on the second monitor and added the Standby Players and the Mixer to it.

After that, ProppFrexx no longer closes when I try to exit the application. Nothing happens.

If I remove either the Standby Players or the Mixer from the Group Container, everything works as expected and ProppFrexx closes normally.

[radio42]

So you are using UAC?!
Please also post your rights for that User…

[John2103]

These are the user rights and settings.

[John2103]

I did another test. I created a new user (John2) and assigned the same permissions (Standard Operator). ProppFrexx still refuses to close when I place the Standby Players and the Mixer inside a Group Container on the second screen, even with this new user.

[radio42]

I mean the rights (not the user settings) of the „Standard Operator“.

I haven’t tested the UAC case yet, will do later…

[John2103]

See screenshots below. I also tested with an admin account. Same results.

[radio42]

Okay - I’ll test it later myself using UAC.

[John2103]

Additional information: I also tested it on another computer, and the results were the same. Therefore, I don't think the issue is specific to a particular computer.