zti display check #167
Merged
zti display check #167
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
najohnsn
force-pushed
the
zti-display-check
branch
2 times, most recently
from
b696cd8 to
5506e53
Compare
Signed-off-by: Neil Johnson <najohnsn@us.ibm.com>
najohnsn
force-pushed
the
zti-display-check
branch
from
5506e53 to
b38b89b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR resolves #165.
There are 2 main cases where ati uses zti:
ONERRORDISPLAYvalues ofALL,HOST, andHOSTCODEWith this PR,
ONERRORhandling will always stack the ati object when using zti. And it will be unstacked when complete.With this PR,
DISPLAYhandling will update the current global ati object when settingDISPLAYand it is necessary. The actualDISPLAYvalue will only be effective when the global ati sessions are the same as the ati sessions for the object being used.