When user compiles from Top File (Ctrl+F9/F10/F11) unintentionally, the results are confusing and not obvious. This was once a feature; however, it has become too common a mistake (especially with PNut using Ctrl+ combinations to compile with Debug; what Propeller Tool does with a mode instead).
Solution: When user compiles from Top File (Ctrl+F9/F10/F11) but none of the open edits are related to said Top File; prompt user before continuing.
If an open edit is related to the top file but the selected edit is not; warn user (different message).
Provide checkbox option to disable the warnings for this session or forever (resettable only through Preferences).
When user compiles from Top File (Ctrl+F9/F10/F11) unintentionally, the results are confusing and not obvious. This was once a feature; however, it has become too common a mistake (especially with PNut using Ctrl+ combinations to compile with Debug; what Propeller Tool does with a mode instead).
Solution: When user compiles from Top File (Ctrl+F9/F10/F11) but none of the open edits are related to said Top File; prompt user before continuing.