MAIN: Issues needing to be addressed for MVP pre-release

[domportera]

Pre-MVP

Issues/Bugs

• Revisit player export (should wait on "Populate project dependencies" for consistency) @domportera
• Right-click -> Add Operator does not work at all @pixtur
• Dragging operators out of and within the Symbol Library does not work or crashes the editor @domportera /@pixtur
• Random paste exceptions on Slot.FirstConnection??
• Popup window input unreliable (particularly for "Blocking" windows)
  • scrolling is still busted sometimes - feels like a Silk.NET GLFW bug
• .NET version sensitivity -@domportera /
  @pixtur
• Selection fence
• Project Settings window does not work at all @pixtur
• Disconnecting from a MultiInputSlot is broken @pixtur

UX

• Re-implement proper layout support for GraphWindow @pixtur
• Open project in Explorer @domportera / @pixtur
  • EditorUi.Instance.OpenWithDefaultApplication(package.Directory) or something like that
• Projects should open immediately when created @domportera /@pixtur
• Render to current project folder @pixtur / @domportera
  • exclude folder from resource and symbol paths (& build paths if necessary)
• Auto-backup needs to catch up with the latest project architecture - preferably ignoring media/image files and read-only packages in backup process @pixtur
  • Should this just be native Git integration? I can imagine having an auto-saved "backup" branch, and saving your project manually fast-forwards the non-autosaved branch to the head and re-saves/commits
• Log spam when using absolute paths with various ops and soundtrack

Technical

• Populate project dependencies @domportera
• Basic version checking @domportera
• Ensure file watching still works properly (code, shaders, images, etc) @domportera
• Clean up/simplify initial project loading @domportera

Post-MVP

UX

• Set project directory per-project (nice to have) @domportera
  • There should be a separate file with two lists - Auto-populated project directories (directories that can contain several projects that should be auto-discovered), and known projects / projects that do not live in the auto-populated directories

Issues

• AudioReaction's (and probably most others') Graph node GUIs no longer display @domportera

[ScreenDream]

As reported on Discord:
When I render to ./Render/Videoname.mp4 the file lands in \Editor\bin\Release\net8.0-windows\Render
I expected it in the same directory as before (\Render in the Tooll root folder) but would also be fine with a folder in the current project folder.

And:
I seem to remember that somebody posted some code on Discord, how an application can request to use the dedicated GPU by default, so that we don't have to set it in preferences for each new version.
I didn't realise right away why my rendering was so slow.
I think this would be super helpful for new and old users.