#Qt does a great job of making me not want to use their stuff for anything outside the intended styles because of how likely it is that code that works now will break in the future, leaving me to have to constantly figure out how to work around it to make it work again. Maybe it's just me programming the All Apps list in a fragile way. Tonight I looked at my stuff again and the All Apps list context menu was misplaced and the scrollbar broke.

#QtQuick #programming #Retiled #RetiledStart

Should I give up and rewrite everything in #Slint with #Rust ? Does it support stuff like #QtQuick 's ShaderEffectSource for displaying part of an image inside the background of a button (that's how I do tile backgrounds like #WindowsPhone )?

#SlintUI #Rustlang

It appears to support it with the source-clip-x, source-clip-y, source-clip-width, and source-clip-height properties of Image:

https://releases.slint.dev/1.5.1/docs/slint/src/language/builtins/elements#image

I'd just have to figure out how to get the background of a button be an image instead of a solid color at runtime.

Builtin Elements - Slint 1.5.1 Reference

Looks like Slint has issues with blurry text if the program is the wrong scale:

https://github.com/slint-ui/slint/issues/4868

I don't want to make programs that have bad font rendering at certain scales. Haven't found anything for context menus yet, either. Maybe I should just keep going with QtQuick until Slint has more stuff I need.

Blurry text · Issue #4868 · slint-ui/slint

Blurry text Although not always, if resized "the wrong way" all slint programs have blurry text; this includes all the executables, the demos in the web browser (firefox, chrome, edge, all of them)...

GitHub