Forum

Can't get to file with dependency missing

I opened a patch and there was an error in a subpatch (different file). As you can see the error was because of a missing dependency since I was opening it the first time on a new machine.

Right-clicking on the node to open it triggered a .NET error though. Only way to get to the file was to open it separately. Annoyingly, you can’t actually tell which file a node is coming from.

Here is the error:

Unfortunately I did not copy the error text and now the error is not happening anymore after fixing the dependency.

ps: who at Microsoft is responsible for the UX of that error window? (my guess: nobody). No resizing, no easy copying of the error text. Leading by good example is not a thing at MS it seems…