Ok... Because ...let's say you create an active object, the main frame being a PNG showing text at low rest. It stays sharp while scalling at runtime. So there's something different for sure between strings and actives ( But using actives will be a pain in the *** since there are a lot of strings in my project )
Android String Automatic Anti-Aliasing?
Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
-
-
the anti aliasing work more in the border of the image, so in a button made with graphic the anti-aliasing is in the border an not touch the inside text, but when you made a text the anti aliasing work in the border of the fonts, right?
-
Well, that's an interesting point of view. But actually, there is just no anti-aliasing at all on active object, even on borders
-
Please login to see this attachment.
Like this, only anti-aliasing on string. But on nothing else ( with are all PNGs on Active objects)
-
Ok, I will do a final change in the runtime, for you and others to text, but it does require that "smooth resizing" is uncheck
-
It is unchecked since the beginning So I guess you'll post a new runtime then?
-
yes, Monday after finish some test here
-
Great, I'll be waiting for that! Thanks a lot Fernando
-
Hi Fernondo,
I tried your new android update, and it still doesn't work. It's a little bit better, but it's not not it.
Here's a picture of what it SHOULD look like, with Smooth Resizing OFF :
Please login to see this attachment.Now, with Smooth Resizing OFF, still the same blury resampling, which only applies to strings (Here, STR, DEF, and all the sharp text are not strings, but PNG... only strings gets blur):
Please login to see this attachment.But with Smooth Resizing ON, there IS anti aliasing, but it's more clear than before... let's say it is almost LESS blury with Smooth Resing ON. Looks like it does not resample, but it does anti-anlias.
Please login to see this attachment.
Would there be a way to do none of them? No resampling and no anti-anlias? ( Like on my first screen shot?)
Thanks again
-
no sorry I don't see possible
-
Argg That's bad Since active objets do not do the same kind of thing, I really don't get how it could not be possible ....
At least, can you tell me which java file in the android runtime is responsible of that behavior? I may try to mod it by myself then, since it logically 100% possible.
( I think it IS 100% possible since it only happens to strings, and it only happens on android runtime ( on windows, everything stays sharp ). ) So the problem is very specific and not "normal" considering the behavior in other runtimes and objet types )
-
Try new beta first
-
Ok I just tried the one you just posted (2852i) and we are on the good way! But something wierd is happening :
Please login to see this attachment.
On the first line it should be written "playerName" and on the second one "5". ( Like on my previous post ).
The resampling is sharp like it should ( ) , but some data is lost. Some pixels are lost. Why is one lost and the other not lost? That I don't know. Maybe still something wrong in the resampling.
For exemple, when expanding, strings forget some pixels. Some unique white pixel (in the text) will become 4 pixel, 9 pixels, 16 pixels ( well, a square, depending on the screen size ). But some pixels are forgotten and 1 pixels becomes 0 pixel.
Again, that kind on data loss only happens on string and never happends on other types of object.
Maybe there is still a little something wrong with the resampling, or i don't know.
Thanks again
-
UPDATE: This data loss only applies to certain fonts, which is kinda wierd. If I use default fonts it does that. But, for exemple, if I use font packer, some fonts are just perfect
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!