Why, when I add a label to a button or panel, can I not see the label text in either the editor or the simulator, but once downloaded to the 9400, it appears as designed - ie the correct colour, size, positioning? I am using PEP latest download 9400 on Windows XP pro. I see in a thread a similar problem but with fuzzy text. this is not my problem, I see nothing.

I'm having the same problem - really weird. Did you manage to find a solution?

Thanks

Dan

Sounds like the Pronto Maestro font is not installed. Try rebooting, then (if that does not work) reinstalling the software.

Also, if it is not obvious, when installing the software, make sure you have administrator priviledges.

I have tried reinstalling, also tried installing the 9600 software, but no change. I have found a PRONTO.TTF font file on my computer in my fonts directory, but this could also be a remnance of my old 980 remote. I have searched the Philips website for a Maestro font download, but nothing there. Would you know where I can download the maestro font file?

Font name is Pronto.TTF. Make a copy of the one you have in C:\windows\fonts and then remove from the Fonts folder. Then, reinstall.

"ProntoMaestro" is the actual font name used to generate the Developer's Guide Appendix B font character table. It is not currently available for download.

Gee McGee.... you solved my dilemma:). Double clicking on a font in the settings/fonts, displays that font in a popup window. However, when I open the pronto font, it shows a blank window, indicating that the font file is empty. Reinstalled the pronto.ttf by dragging it into the settings/fonts, relaunched PEP and I GOT TEXT :)
Thanks:)

I'm having the same problem getting the labels to appear in ProntoPro Edit with my TSU9400. I must not be understanding the above solution.

I have deleted the pronto font from C:\windows\fonts and have reinstalled the ProntoPro Edit program..but it didn't fix the problem?

Hmm.. hope you still have a copy of the file. you need to reinstall the font. to do this do the following:
1 open settings/fonts from start/control panel.
2 also have the WINDOWS/fonts directory open.
3 click and drad the file "pronto.ttf" from the WINDOWS/fonts directory to the settings/fonts directory. This will re-create a link to the pronto.ttf file.
4 check if the font has been installed on your machine by double clicking on the file - "pronto.ttf" in the settings/fonts directory. this will open a window with sample text of the font - "jackdaws love my big sphinx etc"

BTW, I did not have to reinstall PEP, I simply closed the application and reopened it.
Hope this is clearer

Martin,

Thanks for the reply. I'm still having problems. I don't know if the problem is I have Windows Vista..but...I don't have a "settings/fonts" directory under the control panel. I have a "Fonts" folder under the control panel...but this folder is the same folder as "Windows/fonts"

Can you double-click on Pronto.TTF in C:\windows\fonts and see the display? If it shows all white, then you will need to reinstall with admin rights and after installing, try rebooting your PC to see if the font is properly installed upon a reboot.

I have text when I double click on the Pronto true type font. "The quick brown fox jumps over the lazy dog. 1234567890". But the labels still do not show up in ProntoEditPro.

Just curious. On the Label tab of the Properties Dialog for this Panel, what is the Font size set to?

If set to 'None', the text will not display on the remote or in the editor.

Also, on the Properties Dialog where the keyboard is (believe the Label tab), do you have symbols on the keyboard? If so, you likely have a good font, but are likely using as the Font size.

There is one other potential issue (a missing/mismatched GDIPlus DLL) but I won't go there just yet.

Lyndel,

My font size is set to 14. And I do have letters and symbols on my keyboard.

Paul

Well, if that is the case, then there is really no reason you cannot see text unless you have both text color and background color set to white.

Peter DeWildt, might I be missing something else but I think this may indeed be pilot error.