this isnt an sdf one though... its a bitmap font

Ah. I guess i have a SDF one, then ^^'

I don't really know the difference :D

im starting to think that the various settings you use in heaps fonts are very specific to the font

can i use it anyway (to test)?

Sure. I found it in HaxeUI_Base.

great, thanks 🙂

Oh, hi, I suppose we can continue to discuss that issue here, then 🙂

haha, true true... i need to make a repro first, but not gonna do that now... ive another font (as well as yours) so just gonna see whats going on with them

No problem, I can wait. I will be probably using SDF fonts anyway (they look really nice now I know I need to use the alpha channel). I'm testing bitmap fonts because there is an issue with selected text background in Heaps when using SDF fonts, hopefully they can resolved it soonish 🙂

so wrt to this, i think i might change things about a little. Rather than

SDFFonts.register

, i think might have

Fonts.registerSdf

, and also have

Fonts.register

where you can register an actual heaps

Font

with all the settings etc setup... i still havent made a repro yet, but im thinking that the font settings in heaps is very specific to the font data (ie, the file(s)) so it might also be useful to be able to just register any font with the right settings (still thinking about it : ) )

I think, that technically there is no difference between SDF and bitmap fonts. Distance field information is encoded in the pixels of individual glyphs and Heaps uses a different shader that utilises that information but an SDF font still can be used as a normal bitmap font, only the glyphs will be blurry because they're encoded that way. So we need to tell Heaps which type of font it is in order for Heaps to use the right shader. I don't know if this piece of information is relevant or useful to you and you probably already knew, but I wanted to share what I know so far in case anyone wonders what's the difference.

Yeah, using my SDF font without registering it displayed it upside down, like a bitmap one.

i actually didnt know that about SDF vs BMP so nice one 👍

Ian is there a sample app somewhere I can test the ceramic backend with?

nothing defacto no, not really

i would suggest the explorer, but its some bits in there that will almost certainly break

it seems like with the existing backends,

width/height

are somewhat ignored

and you just take the original image's dimensions and work off that

is it "correct" of me to take those values and set the image to them (by doing visual.width = parentComponent.width)

well, the image cx/cy is use if the image is autosized, yeah

if the cx/cy is supplied you should be resizing the image

but it will be passed to you, you should just honour that

90% of the time it will be the same dimentions as the original image, but it might not be, it could be specified by the user, or as part of a %, or as part of a "stretch" operation

what is "cx/cy"?

eg, heaps: https://github.com/haxeui/haxeui-heaps/blob/master/haxe/ui/backend/ImageDisplayImpl.hx#L31-L45

width / height

ahh

so that _imageWidth, _imageHeight will tell you what haxeui wants you to draw the image as