You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys,
I'm not sure if this is bug or more of a feature request - I only have 3 controllers set up but quite a few entries in the playlist panel which means they go off of the bottom of playlist panel and requires me to shrink the controller/failures panel downwards to increase the size of the playlist panel to see them all.
The PC that i run xschedule on has to reboot at 2am every morning, so when I come back to xschedule the next day and reopen xSchedule, the panel sizes have reset to default and I have to resize them again.
I notice in the tools menu that there is an option to reset the windows locations, so am wondering if the panels are meant to remember their location / sizes and are not doing so? and if not, if the ability for it to remember window sizes could possibly be added to a future update please?
Many thanks guys, and keep up the good work!
The text was updated successfully, but these errors were encountered:
Hi guys,
I'm not sure if this is bug or more of a feature request - I only have 3 controllers set up but quite a few entries in the playlist panel which means they go off of the bottom of playlist panel and requires me to shrink the controller/failures panel downwards to increase the size of the playlist panel to see them all.
The PC that i run xschedule on has to reboot at 2am every morning, so when I come back to xschedule the next day and reopen xSchedule, the panel sizes have reset to default and I have to resize them again.
I notice in the tools menu that there is an option to reset the windows locations, so am wondering if the panels are meant to remember their location / sizes and are not doing so? and if not, if the ability for it to remember window sizes could possibly be added to a future update please?
Many thanks guys, and keep up the good work!
The text was updated successfully, but these errors were encountered: