Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#16480 closed bug (fixed)

Shifted text in text controls

Reported by: humdinger Owned by: nobody
Priority: normal Milestone:
Component: Kits/Interface Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

This is hrev54502.

The text in some apps' text controls is shifted down. Examples:

WebPositive locator:
WebPositive's locator

Mail, reading:
Reading mail

Mail, writing:
Writing mail

Worked in Beta2.

Attachments (3)

Web+.png (51.6 KB ) - added by humdinger 4 years ago.
WebPositive's locator
Mail_read.png (26.3 KB ) - added by humdinger 4 years ago.
Reading mail
Mail_write.png (17.8 KB ) - added by humdinger 4 years ago.
Writing mail

Download all attachments as: .zip

Change History (8)

by humdinger, 4 years ago

Attachment: Web+.png added

WebPositive's locator

by humdinger, 4 years ago

Attachment: Mail_read.png added

Reading mail

by humdinger, 4 years ago

Attachment: Mail_write.png added

Writing mail

comment:1 by X512, 4 years ago

Can be a regression caused by hrev54496.

comment:2 by jscipione, 4 years ago

This is most likely caused by hrev54496. However, the bug may be in the app not setting its BTextView TextRect correctly, and is only revealed by hrev54496. Before hrev54496 we were not honoring the passed in TextRect bounds, after hrev54496 we are. You are allowed to position your text rect inside of the BTextView bounds in your app if you want to.

comment:3 by jscipione, 4 years ago

Resolution: fixed
Status: newclosed

Reverted in hrev54530/hrev45431. Fixed again in hrev54549.

comment:4 by nielx, 4 years ago

Milestone: UnscheduledR1/beta3

Assign fix to milestone:R1/beta3, as it looks like this fix will be part of that release.

As we started with the previous beta, we would like to use the Milestone field for fixed tickets to log from which release the improvement will be out. Therefore it is very much appreciated to assign the milestone when closing a ticket as fixed.

comment:5 by nielx, 4 years ago

Milestone: R1/beta3

Reverting ticket update, it seems to be a fix to a regression added _after_ milestone:R1/beta2, so it would be incorrect to add this to the list of fixes in milestone:R1/beta3.

My apologies for the noise.

Note: See TracTickets for help on using tickets.