-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insight import location #536
Conversation
…Location PopUp on image selection
… a popup window now
…eate project/dataset/screen event
Ready for some testing, check that functionality hasn't been broken / changed. |
|
@jburel Testing the switching of users has highlighted that the event fired is not consumed by the importer code and so the groups are out of synch. |
When running as standalone the view and model are discarded and the Importer UI disappears |
The ImporterComponent is discarding the view and model and is not being created again so the UI is not showing. |
…er agent The ImporterAgent is now aware how it is started up (master / embedded mode) allowing for us to refresh the application when a user switch is performed.
@jburel The lastest commits should resolve the issues regarding switching users in Importer standalone and embedded in Insight modes |
@scottlittlewood: last commit
|
Modify the flag of the controls is not necessary. The problem is when you switch between group that when the change should happen. |
@scottlittlewood: PR opened to fix the previous comment. |
Set enabled flag when switching group.
@scottlittlewood: The rest looks good. Standalone works as expected. Just the minor change mentioned in previous comment. |
@jburel Resolved the state checking of the model following your advice. Cleaned up the imports too as I noticed one was unused. |
@scottlittlewood: I found the following error
To reproduce:
|
@jburel I think this only occurs when attempting to directly import in to a Project, not a dataset. The Type check error commit above should fix this as I was able to recreate the issue by reverting the code and attempting to import in to a project. |
@scottlittlewood: selecting a project is a case that we should handle since we can import folder directly as dataset. |
@scottlittlewood: the remaining issues have been fixed. ready to go. |
@joshmoore, @scottlittlewood: Yes few things to be done but they will happen in another PR. Fixed some major usability issues (especially when using to import p/d/i and screens) |
Extract the location dialog and improve the UI & code base. Make Project / Screen selection more obvious.