STimer-appLauncher’nProcWndListTweak: Troubleshooting & Best Practices
What it does
STimer-appLauncher’nProcWndListTweak combines a lightweight app launcher (STimer-appLauncher) with a process/window list tweak (nProcWndListTweak) to speed app switching and manage active processes/windows more efficiently. Typical features:
- Quick-launch shortcuts and hotkeys
- Filtered process/window list for faster selection
- Optional auto-focus or cycle behavior
- Persistent profiles and simple config file
Common problems & fixes
-
Launcher hotkeys not responding
- Ensure the config file defines the hotkey and there are no global hotkey conflicts (check OS hotkey settings and other apps like clipboard managers).
- Run the launcher with elevated privileges if it must intercept system-wide shortcuts.
-
Process/window list missing items
- Check permissions: some processes/windows (e.g., elevated or system services) may be hidden unless the launcher runs with higher privileges.
- Verify the filter settings — overly broad filters can exclude windows; reset filters to defaults.
-
Focus/cycle behavior skips windows
- Reduce debounce/delay settings in the tweak if present.
- Disable any “minimized skip” option if you want minimized windows included.
-
High CPU or memory usage
- Increase the refresh interval for the process list (lower polling frequency).
- Disable visual effects or thumbnails in the list.
-
Settings not saving
- Confirm write permissions on the config directory/file.
- Check for multiple config files (portable vs. installed) — edits may be applied to the wrong one.
-
Conflicts with window managers or virtual desktops
- Enable “respect virtual desktop” or similar toggle if available.
- Test behavior with window manager compositing turned off.
Best practices
- Use descriptive profiles: create profiles per workflow (coding, meetings, media) with tailored hotkeys and filters.
- Assign app-specific hotkeys for the handful of apps you open most often rather than relying on the full list.
- Keep refresh interval reasonable (e.g., 500–1500 ms) to balance responsiveness and CPU use.
- Run with appropriate privileges only when necessary; prefer least privilege for security.
- Backup configs before making major tweaks; use versioned filenames or a dotfile manager.
- Combine with window rules (if supported) to auto-group or pin frequently used windows.
- Document custom filters so you or teammates can reproduce setups.
Quick troubleshooting checklist
- Restart the launcher.
- Check hotkey conflicts and OS permissions.
- Run as administrator if needed.
- Reset filters to default.
- Increase refresh interval.
- Verify config file path and write permissions.
- Test with other window manager settings disabled.
If you want, I can provide sample config snippets for hotkeys, filters, or a profile tuned for low CPU usage.
Leave a Reply