tmpod - Codeberg.org

Mmm I suppose, but I think it is the right call. It clearly shows the user that the control is disabled and can't be interacted with. I always think mouse shapes are heavily underused in most GUIs...

Ah but you used the default shape, I was thinking using the not-allowed one would be better.

Ah you did it already, I was looking into contributing that fix myself xD
Should have said so in advance hehe

You added this to buttons, but shouldn't that shape be applied to all disabled inputs?

Now that the Pure redesign is ongoing, this should be easier, right?

You added this to buttons, but shouldn't that shape be applied to all disabled inputs?

This is where some form of inheritance or mixins in Slint would be really useful :P

Sorry for the delayed response, this flew under the radar for some reason!

Yeah, that was my thought as well! This makes it more expressive and extendible in the future.

Hey, any updates on this? It's very useful to read and reply to comments directly from my e-mail client :)

I know this is already closed, but I just remembered that disabled components (such as buttons) should have MouseCursor.not-allowed.

Yeah, that proposal sounds great! Practical tooltips is something that doesn't seem quite possible in Slint yet, seeing as PopupWindows can only be controlled through function calls, and not...

Right, I was under the (very wrong) assumption that you couldn't easily call Rust (or wtv) code from Slint and get a return, but callbacks can indeed return values, so even if the validation logic...

But for coop I'm open to make it similar to the browser / web. Because it's a custom design, that is something without breaking with the behavior of the template design ;-)

Yeah, I think...

Hey, glad to help!
I'm working with coop on a Matrix-related project :)