Skip to content
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

IOService recognizes a new 3rd state of loading data #430

Closed

Conversation

xulman
Copy link

@xulman xulman commented Feb 6, 2022

The IOService allows (likely among other functionalities) a client-code to be hooked into the drag&drop chain of openers. Each opener in this chain is asked if it supportsOpen() and Object open(final Location source) is called on the first opener supporting the given input.

However, the open() call expects data to be loaded that, in the drag&drop scenario, is directly submitted to uiService.show().

This PR attempts to solve the use case when the open() actually wants to use its own way of presenting the loaded data. The proposal defines a special, unique, signalling object IOService.GOVERNING_APP_STARTED that must be returned from the open() calls in such cases, that is, when 3rd party app is opened on the incoming (dropped-in) file.

This PR works in conjunction with fiji/IO#18

@xulman
Copy link
Author

xulman commented Oct 18, 2023

deprecated in favour of SelfShowableContent -> #473

@xulman xulman closed this Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant