You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to save the current state of the frame controls. This could have a default value and also named settings to efficiently switch between different views. This would have the frame and style that was generated for the view and whatever additional values are needed to restore the controls; by having the actual frame and style, this will be useable by code that uses the tile source without the frame controls.
The settings should be saved in the item record. We could store this in the metadata (in the meta tag), but this adds noise to the UI in a variety of spots, so it might be better to store this as a subkey in the largeImage record, for which we might desire a new PUT endpoint.
The text was updated successfully, but these errors were encountered:
It would be great to save the current state of the frame controls. This could have a default value and also named settings to efficiently switch between different views. This would have the frame and style that was generated for the view and whatever additional values are needed to restore the controls; by having the actual frame and style, this will be useable by code that uses the tile source without the frame controls.
The settings should be saved in the item record. We could store this in the metadata (in the
meta
tag), but this adds noise to the UI in a variety of spots, so it might be better to store this as a subkey in thelargeImage
record, for which we might desire a new PUT endpoint.The text was updated successfully, but these errors were encountered: