09-08-2011 08:52 AM
Hi,
We are using "ActiveRichTextField" component in our application. We have used following constructor:
ActiveRichTextField(String text, int[] offsets, byte[] attributes, Font[] fonts, int[] foregroundColors, int[] backgroundColors, long style)
We have set the Font of text to custom (Bold with small font size).
Problem: when our text characters exceeds more than 32 characters, device default font gets set instead of custom Font. We observed this strange issue on BB 9850 (OS7).
Is it a OS level issue or device issue?
Regards,
Krmlkr
09-08-2011 08:58 AM
09-08-2011 09:18 AM
Thank you Simon,
I am trying to log an issue first time so could you please help me for following:
- Under which project category this issue will come?
- What is a version?
- As there no OS7 devices specified in device list, how should I mention device model?
Regards,
Krmlkr.
03-22-2012 06:07 AM
Any update on this? Is bug already fixed? I also facing same issue.
05-06-2012 12:15 PM
Also encountered this issue using a custom field that extends from ActiveRichTextField that we implemented. It seems that after a certain length of text (it's not 19 in my case. around 32 characters like the one specified in this thread http://supportforums.blackberry.com/t5/Java-Develo
what i observed is that the offsets and fonts are correct right after it's constructed. however, in the paint() method, the offsets are already wrong. nothing calls any of the setText() methods of ActiveRichTextField in between so i'm not sure what else could be modifying the offsets value of the field.
this seems to be a problem when the custom ActiveRichTextField is added to a manager. so could it be a Manager issue?
as a workaround, i've created a wrapper field for our custom ActiveRichTextField and i added the wrapper field to the Manager instead. The wrapper is what will call the ActiveRichTextField's paint method. this works only for displaying the ActiveRichTextField's contents properly. but i cannot figure out yet how to support the proper text highlighting.
is there any solution already from RIM's side on this matter?
09-12-2012 05:53 AM