WINDOWOBJ: Better handling of unknown image objects #1436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2 changes:
If WHEREIS says that an unknown getfn is on FOO-FIE and FOO>FOO exists, then offer FOO in the mouseconfirm. This should get all the support code (e.g. TMAX is offered and loaded instead of TMAX-NUMBER). Issue If GETFN of an imageobj is not defined, try WHEREIS #748. (Sketch files would be renamed to this hyphen naming convention.)
Separately, if the getfn is still not found when the file is opened (so the image object is encapsulated), the encapsulated imagebox fn will upgrade the image when the object is redisplayed, if the getfn has been defined in the meantime. So you can TEDIT a file FOO with a Sketch image object, pass on gettiing the image object during the open, then load SKETCH explicitly. The objects will upgrade when they are redisplayed.