Add Ability to Detect When Logos is Running

[thw26]

This PR aims to resolve #137. It does three things. First, it lists out the kwargs for run_command. Second, I do the same for popen_command. Then there's the big kahuna. As per the commit notes:

• Add logos.py
• Move processes from main to config to avoid conflicts
• Add utils.stopwatch()
• Add system.get_pid(), system.get_logos_pids()
• Add wine.get_wine_user(), wine.set_logos_paths(), wine.check_wineserver(), wine.wineserver_kill(), wine.wineserver_wait()
• Make wine.run_wine_proc() use system.popen_command()
• tui_app menu clean up to avoid locked menus
• Refactoring and PEP8
• Revert Indexer from Vista to Windows 10. Vista prevents it from running.

All of these changes together in that commit work to create a State Manager for Logos. The new config vars in place are perhaps overkill, but they are effective and give us room to use them in the future if ever desired.

Logos.py adds a new class: LogosManager. It also adds in a State class that is just an enum. The manager has a few commands to go with it:

• monitor
• start
• stop
• index
• stop_indexing
• and then I moved the get_app_logging_state and switch_logging functions to the class

The start and stop functions can be called independently. The stop commands are effectively kill commands, and should only be run when shutting down for forcing a shut down.

The class is designed to be updated through the monitor command. The monitor command polls the main Logos and Indexing functions and through their processes determines if the program is running, starting, or stopped. This is maintained through two class variables tracking the state of Logos and the Indexing.

Logos has three processes which are spawned: there is the launching program, which I've called splash—this is what the .exe launches. There are then two other processes: the login command and the actual program, the .exe of which is called LogosCEF. Each of these have to be tracked independently since the latter two are children of the splash, and not of Wine, which means we can't track them through run_command or popen_command.

The way I use this in the TUI is simple.

In the tui_app's main loop, display(), we begin by calling self.logos.monitor(), where self.logos is an app instance of LogosManager, in order to not have empty variables.

Then, during the loop, we run a utils.stopwatch() every 2.5 seconds to determine if the monitor command should be run again. If 2.5 seconds have passed, then we run the monitor() again. After the monitor is triggered, we also run an update to the main menu options to determine if Logos and Indexing should display Run or Stop for the particular program.

---

I also found there were numerous other issues while attempting to fix #142 and #153. Per the commit notes, this PR now also does:

• Fix https://github.com/FaithLife-Community/LogosLinuxInstaller/issues/142. Switch to using tui_dialog.update_progress bar(). Progress bars are now stored as a screen class var.
• Convert most uses of msg.logos_msg to msg.status, and give msg.status an end="\n" flag.
• Comment out winemenubuilder, as it is not working
• Remove duplicate of ensure_winetricks_applied
• Add new TUI/CLI event set/wait calls
• Greatly reduce the time required to complete a system.have_lib() check
• Make tui_app.display() only run logos.monitor when not displaying a python-dialog

[thw26]

My recent push resolves the ability to detect whether Logos is running or not. To do:

• [x] Log in to Logos to verify the .exe is the same
• [x] The current detection code in tui_app, lines 622–625, are not able to differentiate between Logos running and not running. Rather, once the key exists in the dictionary, it is always detected as running. This needs to be refined.
• [x] Add a system-level state manager for whether Logos is running, then make the code poll the state.

[thw26]

After adding the state manager, there has been a regression. I need to figure out why stopping doesn't work again.

• [x] Resolve stop not working
• [x] Move logos.LogosManager.index() to a start/stop method
• [x] The indexing multiprocessing Process does not close properly and causes LLI exit() to hang. This appears to be due to the program launching the Windows Control Panel so as to edit the Indexer's Windows version Changed to threading.Thread and now it closes proper, but it is still calling the Windows control panel for some reason.
• [x] Make TUI menu option Run Indexing change to Stop Indexing when Indexing is running. This is partially resolved, but something still causes the TUI to lock up when hitting run indexing, and thus the menu doesn't update to show that Indexing is running and can be stopped. I'm also not sure if this lock up is related to the indexing being already completed.
• [x] I fixed the indexing detection, but now the main program is not being properly detected by system.get_logos_pids().
• [x] The main program is not being recognized as stopped after hitting the window's X/close button
• [ ] Add GUI portion

[thw26]

I added a commit to fix #153. I also changed utils.stopwatch to accept floats and reduced the TUI app's monitor refresh rate from 3 to 2.5seconds. CPU usage still seems reasonable.