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

Message Composer Overlapping Text #98

Open
gordonparikh opened this issue Dec 14, 2023 · 0 comments
Open

Message Composer Overlapping Text #98

gordonparikh opened this issue Dec 14, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@gordonparikh
Copy link
Contributor

When a whole-sign text rectangle tag is used in a multi-page message pattern in the message composer, IRIS will insert the text from the composer fields incorrectly, leading to overlapping text on one page of the message, and leaving other page(s) blank. For example, using the following message pattern:

[tr1,1,0,0][np][tr1,1,0,0]

will produce:

TEST 1[nl]TEST 2[nl]TEST 3[tr1,1,0,0]TEST 4[nl]TEST 5[nl]TEST 6[np][nl][nl][tr1,1,0,0]

Looking like this in the preview and on the sign:

Page 1 Page 2
TextOverlap_Pg1 TextOverlap_Pg2

This does not occur without the [tr...] tags, for example:

[np]

produces:

TEST 1[nl]TEST 2[nl]TEST 3[np]TEST 4[nl]TEST 5[nl]TEST 6

Which looks like:

Page 1 Page 2
TextOverlap_Pg1_NoTR TextOverlap_Pg2_NoTR

Interestingly, this behavior also does not appear when using a non-default font tag. For example:

[fo10][tr1,1,0,0][np][tr1,1,0,0]

produces:

[fo10][tr1,1,0,0]TEST 1[nl]TEST 2[nl]TEST 3[np]TEST 4[nl]TEST 5[nl]TEST 6[tr1,1,0,0]

And looks like:

Page 1 Page 2
TextOverlap_Pg1_Font TextOverlap_Pg2_Font

When using the default font in a font tag, however, it produces the issue (like the first pair of images). In that case, this message pattern:

[fo11][tr1,1,0,0][np][tr1,1,0,0]

produces the following MULTI string:

TEST 1[nl]TEST 2[nl]TEST 3[fo11][tr1,1,0,0]TEST 4[nl]TEST 5[nl]TEST 6[np][nl][nl][tr1,1,0,0]

This behavior has been observed in several versions back to at least 5.42.2 and can be replicated in the current version (5.49.0). Hopefully it is just a minor error in handling the input from the composer fields. If you have any questions or would like more testing, just let me know.

@DougLau DougLau self-assigned this Dec 15, 2023
@DougLau DougLau added the bug Something isn't working label Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants