Linux: Text Effect is causing crash

[debenham]

I just built a test appimage with the patch and put it up at
https://www.adebenham.com/wp-content/uploads/xlights/xLights-2017.41-3ba16ee.glibc-x86_64.AppImage

Can you please test and let me know how it goes?

[cybi257]

The AppImage looks good so far. The build I did from scratch was crashing quite a bit, but this seems to be doing pretty well and I appreciate the efforts!

Do you know if the Repo version will continue? I really like that as it updates with my system updates and has been very successful in the past. If the AppImage is the only continued option, I'm good with that also, just have to keep on top of it.

The only issue I came across was it was telling me that there was a newer version, so I just said for it to ignore for now.

EDIT: Actually, with the scratch build and the AppImage, using the text effect, I do get some weird behavior that I'm not certain of the source (my system while trying to trouble shoot fonts, xLights itself, or wxWidgets). Sometimes when I use the text effect and OS Fonts, my fonts everywhere in xLights start disappearing. From the test box, to the dropdown menus, to the everything. :/ Any ideas?

Thanks,
-Tim

[debenham]

The repo version will continue - I just didn't update for this test build (it has 2017.41already - I missed 2017.40)

wxwidgets isn't getting a lot of attention anymore upstream and has a number of issues with GTK (which is why we are building with gtk2 rather than gtk3 as that is even further behind)   The font handling seems to be rather 'fragile' and there isn't any way to turn of anti-aliasing
I tend to stick to the XL fonts because at least they are 'solid' (due to AA when you use OS fonts it is never quite as bright)

[dkulp]

wxwidgets isn't getting a lot of attention anymore upstream and has a number of issues with GTK (which is why we are building with gtk2 rather than gtk3 as that is even further behind)   The font handling seems to be rather 'fragile' and there isn't any way to turn of anti-aliasing
I tend to stick to the XL fonts because at least they are 'solid' (due to AA when you use OS fonts it is never quite as bright)

Actually, there are a lot of things going on in wxWidgets.  Unfortunately, getting a release out has not been one of them.   That said, they ARE planning on getting 3.1.1 out in January sometime:

https://groups.google.com/d/msg/wx-dev/FsdAEDISo4k/mgpvYMd7AAAJ

The 3.1.1 codebase has all kinds of chekcs for GTK4 as well as 3 and 2 so some stuff is happening.  On the Mac, we checkout from git and use a specific git hash instead of 3.1.0+patches.   

Not being able to turn off the AA really sucks. I tried a bunch of things down at the cairo/pango level, but haven't found any way to do it.   Not sure if GTK3/4 makes it possible, but it seems like the older libs that GTK2 brings in don't have the ability to do it.

[stampedeboss]

The repo version will continue - I just didn't update for this test build (it has 2017.41already - I missed 2017.40)

wxwidgets isn't getting a lot of attention anymore upstream and has a number of issues with GTK (which is why we are building with gtk2 rather than gtk3 as that is even further behind)   The font handling seems to be rather 'fragile' and there isn't any way to turn of anti-aliasing
I tend to stick to the XL fonts because at least they are 'solid' (due to AA when you use OS fonts it is never quite as bright)

That's why at work we ported everything over to QT and left wxwidgets, not suggesting that for xLights just commenting. 

[cybi257]

The repo version will continue - I just didn't update for this test build (it has 2017.41already - I missed 2017.40)

Awesome. Thank you!

[stampedeboss]

Tonight I upgraded to the repo version 42 and it still has the issue.  I recompiled from within and it works without issue.

[debenham]

Tonight I upgraded to the repo version 42 and it still has the issue.  I recompiled from within and it works without issue.

Can you please send me a copy of a problem sequence so I can reproduce?

Sent from my Nexus 6P using Tapatalk

[stampedeboss]

Here ya go.

[debenham]

I've been testing with the repo version and the appimage versions and it won't fail for me
There must be something different between our systems.
What distro/version are you using?
Does this happen with just that particular font - or with other OS fonts as well?

BTW - 2017.43 is uploaded as appimage (repo version is building currently) so maybe re-test?

[stampedeboss]

Let me test it this morning.  I’m using Mint 18.1 KDE edition.  It also fails on Neon.  I haven’t tried it on my other images.  It happens with any other os font.


Sent from my iPhone using Tapatalk Pro

[stampedeboss]

Happy to report that the sequence was able to be save and fseq generated without issue on .43.  I knew that it would eventually get fixed.

So Gillrock, the answer now is my pictures and text look great, and it runs very fast on my system.   Just poking fun, thank you for all that you guys do!!

[Gilrock]

https://www.youtube.com/watch?v=nyyiQqEKyFQ

[stampedeboss]

https://www.youtube.com/watch?v=nyyiQqEKyFQ

Perfect response!