-
Notifications
You must be signed in to change notification settings - Fork 52
track: Some (small) changes before 0.8 #758
Comments
There's no need to move to the new 4.10 widgets, as the old ones will be removed in GTK 5, which isn't even in the workings yet. Porting now would make Gradience incompatible with most native users, so I would wait with moving to new widgets until at least 4.10 will be available in most distributions. Check out October post on GTK blog talking about 4.10 deprecations for more info: https://blog.gtk.org/2022/10/ |
This can be fixed by making rename button the first button in a row, this is also a good chance to use the new layout [rename / apply / star] I have tried to do this but for some reason rename button disappears after clicking on it, so I guess I did something wrong :) |
No, I mean the color button in gradience itself can be dragged on the other button, and it will copy the color, but hex itself doesn't respect this |
## Description Replace logout message with toast [HIG](https://developer.gnome.org/hig/patterns/feedback/toasts.html) Fixes #758 ## Type of change <!-- What type of change does your pull request introduce? Put an `x` in the appropriate box . --> - [ ] Bugfix (Change which fixes an issue) - [ ] New feature (Change which adds new functionality) - [x] Enhancement (Change which slightly improves existing code) - [ ] Breaking change (This change will introduce incompatibility with existing functionality) ## Testing - [x] I have tested my changes and verified that they work as expected <!-- Make sure you did this step before marking your PR as ready for merge. -->
To-Do
A few things that would be good to do before 0.8 but are not blockers, tracked in this list to not forget about them
translator-credits
, I have made it vary from lang to lang, but now link/mail is broken as Weblate is confused by using XML syntax in Python fileThumbnail Colors
Simplify welcome window by removing useless steps like selecting theming options and installing themes pagesAdditional Context
No response
Did you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: