Text in Tabs Appears Clipped in Uppercase

  • Follow


I'm working in FileMaker Pro Advanced 9.0v3 on the Mac OS.  I find
that when I add a Tab Control, the text labels appear correctly unless
I apply the Uppercase style (my preference for tabs).  In uppercase
the text is clipped at the end, so that a word like "Billing" appears
as "BILLIN" (missing one letter) or "Forwarder" appears as
"FORWARD" (missing two letters) even though there's plenty of space
left for the whole word.  This happens regardless of the font (I
tested it using Arial, Helvetica and Verdana) or justification
(appears clipped in all four formats) or tab width (the same for every
setting).  Also, just FYI, the indent is set to 0.00 for all three
options plus, let me mention again, the labels are not clipped when
Uppercase is unchecked even if I use a larger font size that takes
more room, so it appears not to be an issue related to some other
setting (such as indent, justification, font).

Has anyone run into this?  Does anyone have a solution other than
having to add separate text labels manually for each tab, which would
mean typing in all text labels for each tab on every layer of the tab
control for every layout where a tab control appears?  Not that this
is a problem initially, but it's not a good solution for efficient
database maintenance.

Any good recommendations much appreciated.

Thanks.
-J.
0
Reply jahnbigbooty (106) 3/12/2009 2:22:06 AM

On Wed, 11 Mar 2009 19:22:06 -0700 (PDT), jahn wrote:
>  This happens regardless of the font (I
>  tested it using Arial, Helvetica and Verdana) or justification
>  (appears clipped in all four formats) or tab width (the same for every
>  setting).

FMP7 had an extremely poor font rendering.
FMP8 broke monospaced fonts.

I'd guess that the font rendering is broken - FMP does not rely on the
system itself, but *tried* to make it better.

I guess they succeeded concerning display speed, but they failed on many
details out of the mainstream - and UPPER or kapitals are not that far
out of the mainstream one should guess.

Send them a bug report, but don't expect a fix.
Use images if you need these UPPERs.

- Martin
0
Reply t-use (417) 3/12/2009 9:35:05 AM


On Mar 12, 2:22=A0am, jahn <jahnbigbo...@yahoo.com> wrote:

> Any good recommendations much appreciated.
>
> Thanks.
> -J.

Hi J

I've encountered the same issue. My solution is to pad the text with
three to four space characters on either side e.g. "    Heading    ".

Regards
Kevin
0
Reply donotusethisaddressr (14) 3/12/2009 3:53:55 PM

On Mar 12, 8:53=A0am, Roz is learning to draw
<donotusethisaddre...@gmail.com> wrote:
> On Mar 12, 2:22=A0am, jahn <jahnbigbo...@yahoo.com> wrote:
>
> > Any good recommendations much appreciated.
>
> > Thanks.
> > -J.
>
> Hi J
>
> I've encountered the same issue. My solution is to pad the text with
> three to four space characters on either side e.g. " =A0 =A0Heading =A0 =
=A0".
>
> Regards
> Kevin

Thanks, Martin and Kevin.  Glad to know someone else is having the
same problem.  I didn't realize FMP had so many troubles with font
rendering.  The padding is an excellent idea.

Best,
-J.
0
Reply jahnbigbooty (106) 3/12/2009 4:44:31 PM

I wasn't able to reproduce your problem when defining the labels with
the keyboard set to ALL CAPS and the Style set to 'Plain
Text' (Format>Style>Plain Text). However, when I fooled around with
settings and set Style to UPPERCASE and typed a long string in lower
case (for a tab label), then I did get the error you speak of... I was
able to resolve the problem of truncation by changing Style back to
'Plain Text' and retyping the label in ALL CAPS (though it didn't take
immediately in this one case ... after changing the label's text, or
whatever else I did, then it "took")
0
Reply obeechi (1) 3/16/2009 12:43:52 AM

That solution makes so much sense I want to smack my head for not
thinking of it.  Thanks for posting.
0
Reply jahnbigbooty (106) 3/18/2009 1:40:04 AM

5 Replies
45 Views

(page loaded in 0.178 seconds)

Similiar Articles:









7/17/2012 10:50:51 AM


Reply: