Open aonanam opened 7 years ago
@aonanam Any pointers on what files could be related to this issue?
@kestaskk Would have the best idea.
It seems the page uses the correct project's default DesignMINT.uf, even though it requires the user to specify the project again. So it "knows" which project it's in, you'd just need to link the known DesignMINT.uf to the folder above it (the selected project) to inform Neptune which project we're in by default. So a handoff seems to be there, but it's just not informing the whole system.
For loading up the .uf created from the Specify page, some new info may be needed to be added to the Specfiy->Design handoff (upon continued to the Design page after creating a .uf on the Specify page)
Adding info to this issue: If you name your .uf as DesignMINT.uf, Neptune will point to the newly created file on entering Design from Specify. So Neptune is definitely grabbing the DesignMINT.uf from the correct project.
I'm going to need a runthrough of the whole process, this is confusing.
Coming from the Specify page where the user created their MINT file, the Design page forgets what project and file the user has created, and reverts to the default DesignMINT file. This means the user must either click their MINT file twice, or their project once then their MINT file once (to first load the project then load the file).
The handoff from Specify to Design could inform Design what MINT file was created, as well as what project the user is working in. These could then be selected by default. This would improve the fluidity of the tool.