02-04-2011 03:24 PM
You could always use the client QNX dialog library that has the same look and API as the native QNX dialog package.
02-04-2011 06:08 PM
Renaun, thanks for digging into this! I was able to duplicate it, sort of, on Windows and using the command line tools.
Basically including one extra option on my command line works:
amxmlc -external-library-path= -output MyTest.swf MyTest.as
With nothing immediately after the equals sign that overrides the air-config.xml entries for "external-library-path", resulting in both libs/air/airglobal.swc and libs/air/qnx-air.swc being statically linked (and thus, I infer from your blog post, able to be shadowed by local code in qnx/pps/PPSChannel.as).
The difference in our results is that with my setup, the font appears to be Times Roman instead of whatever you have. I suppose your previous experiments with getting the BBAlpha Sans font on your host machine make the difference.
02-04-2011 07:25 PM
Yeah I do have the BBAlpha Sans font installed on my machine so that would be the font difference. Kudos for figuring out the command line equalivent of the solution.
02-04-2011 08:31 PM
Nice stuff! Thanks man,
Disagree though. The default components are pretty ugly, and QNX actively promotes skinning every other component, so why shouldn't we also skin dialogs?
02-09-2011 09:26 AM
How do I also install BBAlpha Sans on my computer? I wasn't able to find it through Googling and the only other possibility seemed to be installing a different Blackberry SDK at something like 500Mb! Would there be any chance you could post it on here?
02-09-2011 09:40 AM
In this thread, you will see that I attached the font in one of my responses.
Unzip it and add the font to your system like any other font.
02-09-2011 09:52 AM