The Playout and Radio Automation Solution
https://www.radio42.com/proppfrexx/forum/
https://www.radio42.com/proppfrexx/forum/viewtopic.php?t=3896
I just tried it without recording a show. when the windows are undocked and on another monitor, if i attempt to close propfrexx then it asks me if i want to close the programme. i click yes, it closes whatever playlist i have opened, but the application itself doesn't close. If i click the close box, nothing happens, however if i then redock the widows and click the close box then, it asks me again if i want to close proppfrexx. i click yes, and this time it doesn't. The problem only seems to occur if the windows are undockedradio42 wrote: 25 Oct 2025 16:19 I can not reproduce the issue here.
Does this only happen, if you record a show? Ie. if you move the windows but don’t record a show, it does not happen?
What are you exactly doing to record a show? Just open a playlist and press REC on a mixer channel?
the playlist wasn't playing, it was stopped and i had saved it. The problem only seems to occur after i physically undock the find/mixer window group, without docking it again, and after some activity. if it is waiting for a dialogue response, which is quite likely, the dialogue waiting for response doesn't show up/ I've noticed that happen with other software. i shall attempt to reproduce the error by opening a session, undocking the mixer/find window group, opening a playlist, making changes and trying to close propfrexx, see if that causes the issue. I'll get back to you with the result.radio42 wrote: 30 Oct 2025 16:28 I can still not reproduce the error.
But note, that when you close ProppFrexx but also currently play a playlist window, that you might get 3 dialogs, which you all have to confirm resp. answer correctly.
1. Dialog: Confirm, that you want to close ProppFrexx - YES
Screenshot 2025-10-30 160630.png
2. Dialog: Confirm, that you want to stop the currectly playling playlist - YES
Screenshot 2025-10-30 160646.png
3. Dialog: Confirm, that you want to save the playlist - YES or NO
Screenshot 2025-10-30 160659.png
If you cancel any of the above dialogs, ProppFrexx won't exist.
This happen to me, no matter, if I dock or undock any window panels. I.e. even, if I undock the mixer panel and the Find panel to another secondary monitor and confirm the above dialogs (e.g. YES, YES, NO) ProppFrexx would close gracefully.
So it is strange, why this is not the case on your end - are there are error messages or a like?
i tried it. it did not produce the error, the dialogue asking me to save the playlist appeared.fjb59 wrote: 01 Nov 2025 12:56the playlist wasn't playing, it was stopped and i had saved it. The problem only seems to occur after i physically undock the find/mixer window group, without docking it again, and after some activity. if it is waiting for a dialogue response, which is quite likely, the dialogue waiting for response doesn't show up/ I've noticed that happen with other software. i shall attempt to reproduce the error by opening a session, undocking the mixer/find window group, opening a playlist, making changes and trying to close propfrexx, see if that causes the issue. I'll get back to you with the result.radio42 wrote: 30 Oct 2025 16:28 I can still not reproduce the error.
But note, that when you close ProppFrexx but also currently play a playlist window, that you might get 3 dialogs, which you all have to confirm resp. answer correctly.
1. Dialog: Confirm, that you want to close ProppFrexx - YES
Screenshot 2025-10-30 160630.png
2. Dialog: Confirm, that you want to stop the currectly playling playlist - YES
Screenshot 2025-10-30 160646.png
3. Dialog: Confirm, that you want to save the playlist - YES or NO
Screenshot 2025-10-30 160659.png
If you cancel any of the above dialogs, ProppFrexx won't exist.
This happen to me, no matter, if I dock or undock any window panels. I.e. even, if I undock the mixer panel and the Find panel to another secondary monitor and confirm the above dialogs (e.g. YES, YES, NO) ProppFrexx would close gracefully.
So it is strange, why this is not the case on your end - are there are error messages or a like?