Empty "blank" characters not showing when using UseD2D=1

[Virginityrocks]

I've tried various encodings, but I generally stick with UTF-16.

Does this trailing spaces feature only work when I use UseD2D=1? Or does it work with UseD2D=0 as well? I haven't tested that. I'm currently set to UseD2D=0.

Edit: I just checked. Trailing spaces work with UseD2D=1. I made the assumption that it would work with both UseD2D =0 and =1. The 3.0 changelog didn't specify.

[jsmorley]

It only works with UseD2D=1

[Virginityrocks]

Shoot. I can't use UseD2D=1 in its current state. How is the development going on that front, by the way? It seems to work well for me. Once UseD2D becomes default I will make the changes to my suite.

[jsmorley]

Shoot. I can't use UseD2D=1 in its current state. How is the development going on that front, by the way? It seems to work well for me. Once UseD2D becomes default I will make the changes to my suite.

We have a fairly large hurdle to get over in order to reconcile some padding and spacing issues between GDI+ and D2D, but are working hard on them. I don't have any ETA just now, but hope it won't be too much longer.

In the meantime, we will look at what can be done with this specific issue to make GDI+ and D2D behave the same with leading and trailing spaces.

It should be noted in general terms that AFTER we have D2D working the way we want, and make it the default (for systems that support it), there will be TONS of changes and improvements that we will make that will only be supported with UseD2D=1. I only say this so folks can start planning for a time when they will be putting out skins that will need to be set to "Windows 7 or better".

[Virginityrocks]

Perfect. That would make the transition easier. I can't wait. It seems D2D really improves the appearance of fonts, especially thin fonts like Segoe UI Light.

[Brian]

Trailing whitespace when enclosed in quotes will now work for both D2D and GDI+ rendering as of the next beta release.

-Brian

[Virginityrocks]

aw yeah. Thanks, Brian!

[sa3er]

You can also use Alt+0160 for invisible space character.

[Virginityrocks]

Yes, but I don't like that when the encoding changes, the spaces become a german A or a square.

[iNjUST]

Trailing whitespace when enclosed in quotes will now work for both D2D and GDI+ rendering as of the next beta release.

-Brian

I think I found a bug with this update, but I'll write here to avoid making a whole new thread over a small issue: I think an unintentional consequence of this is that now #CRLF# is now treated as a space character of sorts. I noticed this in a skin where I have a Right-aligned string, with a line break, such as:

Code: Select all

[SampleMeter]
Meter=String
X=100
Y=0
StringAlign=Right
Text="Some#CRLF#Text"

In 3.0 r1995, the last character before the line break (in this example, the "e" in "Some") is aligned at the right edge of the meter, as is the last character in the second line (the "t").

In 3.0 r2012, there is a space after the last character before the line break, and the two lines are no longer equally aligned at the right edge.