Solved TextBox rendering issue (possible a bug)

[backcountryprogrammer]

Attached is a DB with a form that shows two text boxes. The only styling applied to the text boxes is the border width; everything else is default. One text box has event handlers setup for Got/Lost-Focus. In the event handler I set the color of the textbox. I observe that this screws up the rendering of the text box (see pictures). If I don't modify the text box properties then it renders fine. This appears to bug in the renderer.

If I leave the border width at the default, everything renders fine.

Anybody seen this before?

 

[arnelgp]

i don't see any anomaly.
the second image, the text are all selectected.
if you click very fast, access will highlight (select all text from the textbox).

another thing you can use Conditional Format on that textbox instead of
a bunch of code.

 

[backcountryprogrammer]

i don't see any anomaly.
the second image, the text are all selectected.
if you click very fast, access will highlight (select all text from the textbox).

another thing you can use Conditional Format on that textbox instead of
a bunch of code.

The second picture shows how the text is truncated; the lower 1/3 is missing. Does this not happen for you when you run the attached DB?

It appears that the whole text in the box is shifted down a little bit when the box gets the focus. It jumps back once the focus is lost. This only happens when the event handler modifies the text box. The top box has no event handler setup to demonstrate that there's no problem. Also, the problem goes away when I set the border width back to the default.

 

[Gasman]

 

[CJ_London]

works OK for me as well

I would say the font size is too large for the height of the textbox (or the textbox height is too short)- in both cases on the left, the bottom part of the letter g is cut off - same for Gasman. You might also want to look at your margin sizes for the controls (particularly top margin)

 

[MajP]

Why have such a large top margin in such a small text box? And if you simply reduce the top margin

 

[backcountryprogrammer]

works OK for me as well
View attachment 116957 View attachment 116958
I would say the font size is too large for the height of the textbox (or the textbox height is too short)- in both cases on the left, the bottom part of the letter g is cut off - same for Gasman. You might also want to look at your margin sizes for the controls (particularly top margin)

Interesting it works for you. Both text boxes show the same vertical text positioning. You run the DB I attached I assume.

When I move the focus to the Text1 box (I color it blue in the event handler), the text shifts down a tiny little bit which makes it become truncated. I move the focus back to the Text0 box then the text resets itself to the proper vertical position (as shown in my first pic). The Text0 box doesn't show this behavior and the text stays at the same position no matter whether it got the focus or not (as expected).

Of course I can make the box larger or adjust the margins but that is not the point. The text still shifts for me which it shouldn't.

Perhaps I will try to update to a newer version. I'm on semi-annual enterprise.

 

[backcountryprogrammer]

View attachment 116956

Both text boxes show the same vertical text positioning which it does not for me. Yes in your case, the box or margin need to be adjusted but it is consistent between the two boxes.

 

[backcountryprogrammer]

Why have such a large top margin in such a small text box? And if you simply reduce the top margin
View attachment 116970

I see, all positioned vertically the same.

 

[backcountryprogrammer]

I updated to monthly-enterprise channel but the problem persists.

I noticed that when I click in the Text1 box the font doesn't shift vertically. It only does that when I Tab into the text box. It's clearly a bug so I'm closing this now.

 

[Gasman]

I updated to monthly-enterprise channel but the problem persists.

I noticed that when I click in the Text1 box the font doesn't shift vertically. It only does that when I Tab into the text box. It's clearly a bug so I'm closing this now.

So report it?

 

[backcountryprogrammer]

So report it?

I have no idea where to report it to. Is there something like an official bug report portal?

I'll try it on a different machine this week. Perhaps it works there as expected. I do my MS Access stuff in a VM perhaps this has something to do with it.

 

[Gasman]

Someone here will be able to post a link.

 

[GPGeorge]

I have no idea where to report it to. Is there something like an official bug report portal?

I'll try it on a different machine this week. Perhaps it works there as expected. I do my MS Access stuff in a VM perhaps this has something to do with it.

There's an in-app way to provide feedback.

 

[isladogs]

Tested in A365 Beta channel. Same as everyone else here, the results are OK for me also

With 5 people all saying there is no issue, I really don't believe there is a bug here.

 

[backcountryprogrammer]

Tested in A365 Beta channel. Same as everyone else here, the results are OK for me also

View attachment 116984
With 5 people all saying there is no issue, I really don't believe there is a bug here.

I see. Just weird this only happens for me. My VM is setup specifically with only Access and Excel, nothing else. System is fully updated and I removed all unnecessary bloat. I'll try on a different production machine but I bet it will work there after all the input I got here.

 

[AHeyne]

Do you maybe have any scaling in the Windows screen settings other 100%?

 

[backcountryprogrammer]

Do you maybe have any scaling in the Windows screen settings other 100%?

Yes it's a HiDPI screen. It's at 250%.

 

[GPGeorge]

Yes it's a HiDPI screen. It's at 250%.

Try at other scaling, then. That way you confirm whether or not scaling is the source of the problem in this environment.

 

[backcountryprogrammer]

Try at other scaling, then. That way you confirm whether or not scaling is the source of the problem in this environment.

Good call but I tried that already at 150% scaling and it still does it.

I do my Access stuff in VirtualBox. The version 7.1 has a bug in which the selected resolution is always off by 1 pixel, so you get weird resolutions like 1919x1199 instead of 1920x1200. Perhaps that throws something off in the renderer in which case it might not have something to do with Access itself but the underlying subsystem. I'll only know once VirtualBox fixes this annoying bug.