Having cloned libNougat. When I try and open the project, the solution gets loaded but if I click on files in the solution explorer nothing happens. Also build doesnt appear to do anything.
The editor window just says "Files /Users/JohnMoshakis/Documents/develop/libNougat/Source " with reveal in finder underneath.
There doesnt appear to be anything in console.
In other projects I have open, I can see file contents and build.
Also when I click on the red x in the top left of the project, Fire hangs.
I cannot reproduce the issue with the projects you sent, nor can i find anything obviously wrong with the code in a dry review — all looks in order. Does this fail for you in every project now, or just thee two? if the former, what changed since the worked fine (updating to latest Fire beta?) of the latter, what’s different between these two projects and your others?
can you also send me a s screenshot for
The editor window just says “Files /Users/JohnMoshakis/Documents/develop/libNougat/Source " with reveal in finder underneath.”
Ok, i know what’s going on. The latest Fire beta is complexity broken, because off this.
Essentially, i had to work around a compiler regression that required me to provide a dummy implementation for some optional interface methods. Having this dummy implementations causes other parts of Fire to misbehave. It seems tis will only trigger if you select a Folder node, and once you do, you’re screwed.
Workaround: close Fire, delete the .user and .cache files, and don’t any nodes except actual source files in the tree view. I’ll work on a workaround for the workaround and post an updated beta, but its might not be until tomorrow.
That, or go back to .1891 RTM, which does not have this issue.
My apologies for this, and thanx for reporting!
Update the sad thing is that the issue i was working around was actually already fixed for Friday’s alpha compiler, but Carlo didn’t tell me
.1891 should not have the issue, with or w/o the .user file. Deleting the .user file would just prevent .1895 from re-selecting the folder node (and thus immediately getting stuck again).