@Scott: It's a device font. There is a nice free font displaying app called FONTS! It will show you all the fonts of the device, even with samples.

@OderWat: Been there, done that. And guess what... we have already complained about it. So you are not the first who discovered this. How you can fix it? Man that is a difficult question. Use a different positioning when you deploy to the device. Work around it till Ansca finds a way to fix it. Easy, isn't it. :-)

We do have a case opened on it, but haven't gotten to actually fix it yet.

@Fogview: The second three test cases are meant as I wrote them. By setting the y value after creating the object with y=0 at create time... to illustrate the change in the reference point.

This is also what I use what I use in my code.. .because this way I have easier positioning for my case which needs to place numbers on some kind of grid. Which is easier with the reference being the center of the object. The reference line itself was only roughly placed.

@MikeHart: Well... If we can fix it in our code... Ansca should be able to fix it to hopefully.

This needs to be fixed asap in my eyes! These are basics which should work as one expects. I spent hours today to find and universal fix :(

I have about between 100-200 texts (mostly just one number per object) on the screen in different font-sizes and font-styles and I was going to implement the possibility of theming into the game which means that the font can be changed too.

Well I had conditional code for different fonts out of my prototype code (written on windows in python some months ago) because I experimented with fonts. So I create a little "onDevice" true/false and wrote some conditional code trying to keep the needed changes minimal.

Basically it seems as if I have to substract about 1/8 of the fontsize for the y position to have consistent positioning (roughly tested and by eye only)

The change of the reference point when using the newText(...,x,y,...) and manipulation of obj.x, obj.y after the object is created also seems a bit inconsistent to me?

BTW... is there a way to see the open cases!? I only get error pages when I access the bug-tracker which is listet in the sticky .. and get permission denied errros for some links I got in emails for new opened cases.

> is there a way to see the open cases!?

We're working on that. Unfortunately the solution we chose doesn't do everything we want, and we're looking at transitioning to another system.

Ah ok... we use trac for our projects .. but more because I like a bit(e) of python for lunch :)

Something else but a bit related... would it be better... performance wise to have all little images instead of the newText() objects?

@OderWat

I thought that might be the case with your second set of fonts but I didn't notice much difference. I too had problems positioning text with newText and started using ui.newLabel instead.

I think the previous text rendering bug is #126.
http://developer.anscamobile.com/forum/2010/03/16/simulator-rendering-problems

Tom

@Fogview

ui library is to much overhead for this... After all I just want to place single Digits on the screen and it is just "Lua".

It uses the type of positioning I showed in my second example together with using the stageHeight of the object.

1

labelText.y = top + labelText.stageHeight * 0.5

I like your onDevice detection code. I modified it a little to check for the Icon.png file which should be in every build.

Thanks,
Tom

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

---- Check if running on device or simulator ---- onDevice = false                -- assume running on simulator local path = system.pathForFile("Icon.png", system.ResourceDirectory) if path and string.sub(path,1,6) ~='/Users' then         -- Found device if Icon.png found and not in /Users folder         onDevice = true end path = nil -------------------------------------------------   if onDevice then         print("Running onDevice ...") else         print("Running in Simulator ...") end

@fogview

Hehe :) yeah... funny thing is that my project currently has no icon :-P

Another very easy way is something like this:

1 2 3 4 5 6

// first line! if system.getTimer() > 10 then  // device else  // simulator end

Wow, I'm running into the same problem and it's still not fixed. WTF?

Anyone figure out a good way of measuring the offset to fix the font position?

views:3023 update：2012/2/13 9:11:28