timsorbet/mfaktx-controller

mfaktx-controller's Issues

pause/slow detection might not work

Pause/slow detection doesn't work if the pause and slow lists are both empty when you start the controller.

add 'stop immediately' button

It would be useful in some circumstances to allow a user to bypass their declared timeout (time to wait to kill mfaktx before forcing it to close) and close mfaktx immediately, possibly by a button that only appears when in the "Stopping" state. (my use case is when running mmff, where a single class can take ~7 minutes; sometimes I want to switch speeds after the current class, and sometimes I want to switch immediately)

Incorrect speed can be chosen

If you cancel the screensaver/auto-off shortly after it starts (e.g. while in Stopping (Medium) state), the idle detection will end up making the speed Fast, not Medium.

Scrolling can jump

Scrolling can jump to the top when you aren't at the very bottom. Workaround: check and uncheck the "Select Mode" box (or just keep it checked); for reasons I can't fathom it temporarily fixes it.

add SlowWhileRunning

Delay switching speed due to idle

E.g. wait until 5 seconds after the screensaver is enabled to switch to Fast. This will make the app behave better at times when the user is at the computer, perhaps watching a video, and accidentally lets the screensaver kick in. Instead of immediately starting the switch to Fast, thus wasting a few seconds of processing due to mfaktc's self test, wait a few seconds to see if the user cancels the screensaver or not.

show GPU/instance in title bar

Option to show which GPU is being used in the window and/or title bar.

In-UI modification of Pause/SlowWhileRunning

E.g. a list of processes that most likely you'd want to pause or slow while running (memory usage? easy to measure, high correlation), with a way to select process(es) and add to pause or slow list. Perhaps a full "settings window" to modify other settings, too?

output lines don't always appear immediately

When mfaktx outputs certain information, e.g. startup lines and the message that a shutdown was requested with ^C, it doesn't appear immediately. Most likely because I'm only listening for a full line to be output, and mfaktx writes it to the console in a way that doesn't trigger this.

speed can become stuck

"One instance is set to change speeds based on both conditionals and it changes speeds all of the time, for DPMS, gaming and general browsing. This instance, after a few days (Or cycles?) will get stuck on a speed and will not allow us to stop it or change the speed. (We kill it in the task manager.)

It only happens after several days so we are okay with rebooting occasionally."

single ini file or merged ini files

Configuration could be simpler, some possibilities:
Use a single ini file for the basic configuration, and simply prepend or append the GPUSieveSize when forming the ini file.
(related to above) Allow user to set GPUSieveSize values from controller, either instead of slow/medium/fast or as a way to set which three values you'd like as your slow/medium/fast values
Set a 'common' ini file, and slow/med/fast ini files; append the two together to create the one that will actually be used. The slow/med/fast might include only the GPUSieveSize, and the 'common' would include everything else.

PauseWhileRunning

Add option to pause while running

controller kills wrong/both mfaktc instance

http://www.mersenneforum.org/showthread.php?p=352557#post352557
"whenever I change speed, it kills the mfaktc running on my other GPU"

improve add to pause/slow while running options

The interface could be improved by putting the list of active processes on the window with the list of processes to pause/slow while running (there's no need for them to be separate, it loads fast enough, so it, and the Add/Show List buttons are just a confusing extra click)

status can show Running (Stopped)

Choose font

Option to specify a font for the console output.

improve title bar text order