1
Support and Feedback / General slowness - example switching MC from one monitor to another
« on: March 25, 2018, 23:12:03 »
Hi,
Recently I've been starting to see slowness with MC just doing basic functions like browsing folder or dragging files. An activity that can take about 20 secs is just switching MC from one monitor to another - when it does this I do get a "Not Responding" message in the title bar temporarily while it catches up.
I saw mention of users enabling the Debug log to investigate - where is that stored once enabled?
I am running v7.7 (build 2404) where I've noticed this happening but it has been a while since an update was released so it could be changes I've made on my system.
Thanks.
Recently I've been starting to see slowness with MC just doing basic functions like browsing folder or dragging files. An activity that can take about 20 secs is just switching MC from one monitor to another - when it does this I do get a "Not Responding" message in the title bar temporarily while it catches up.
I saw mention of users enabling the Debug log to investigate - where is that stored once enabled?
I am running v7.7 (build 2404) where I've noticed this happening but it has been a while since an update was released so it could be changes I've made on my system.
Thanks.

Yes I know - its more of a gripe around the implementation of the "Minimize to tray instead of closing". Not only does it disable the window close button (instead of minimizing to tray) but you would expect if it is in the systray a system shutdown would result in MC saving its settings before exiting. I'm sure no one goes through all their systray apps and closes them all individually before shutting down their PC?