sgrottel / little-starter Goto Github PK

Actively delay the Process.Start by some milliseconds can help avoid some lock-up problems with FireFox and Websites requesting basic authentication.

Each Item should show it's progress when "the starting" happens:

• Delayed with Count down (Progress bar?)
• Starting (waiting von confirmation)
• Started (confirmed)
• Error

This replaces the generic log block in the lower left.

Try to keep item height minimal. Info should be added to the right, or replacing the informational second line.

Observed several times on my second machine. Not reproducible!

Likely a crash/exception sometimes happening when trying to start a process, or the little-starter process being shut down (security software)

• Log writing must be improved that at least partial logs already have been written when this happens -- Since this app is not time critical, logs can be flushed on every message
• Add more log messages during the start process to track down the issue.

For now, explicit icon referencing in the yaml only. No automatic detection/extraction, because pain.

Anything which can be loaded directly into an ImageSource.

No conversion for now.

The window should automatically increase it's size to fit all content without scrollbars, if possible.
A maximum auto-increase window size could be 2/3 of the desktop size.

For some processes, it does make sense to only start one after the other, e.g. they all do massive operations on the same harddisk and would only slow each other down (e.g. updating the everything index, and performing massive search queries). It does make sense to chain those process runs one after the other, e.g. specify that one process should wait for the END of other processes.

If:

1. filename is an absolut path, aka start with a drive (think about whether UNC is worth it. Likely not.)
2. that drive is not available

then mark (somehow) the Action as not available.

• A -- All
• N -- None
• F5 -- Refresh
• (Ctrl+)Enter -- Action
• ESC -- Close

Add code to confirm starting of the child processes.

• Poll state changes of the process handle obtained on start
• OS Hook to be called back on new processes?
• Process polling for some time after the start?

Enable an item if another item is also enabled.

This helps with items which are evaluated to be unavailable due to unavailable file system path, for example.

Does not work transitive. Otherwise we would need to take care of cycles.

Option to write log files, and then log exceptions on process invocation.
Do not stop invocation loop when one process raises an exception.