-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of GTK-related issues and deprecations #2014
Comments
Most of the Windows-exclusive issues should be fixed once https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4252 is merged. |
GTK 4.6.4 (Arch Linux, gtk4 1:4.6.4-1) The two only errors i got now @mathiascode
Still missing logos but will report to arch repos as a bug report, possible missing logos? https://bugs.archlinux.org/?project=1&string=gtk4 |
When I press enter to enter a search query in someone's share list when using GTK 4.6.5 (from Arch 1:4.6.5-1) (libadwaita or not), the tree view does not jump to the folder. Instead, it just jumps down the page a little bit like when you press space on a long web page. Then if you do it enough times the behaviour is a little bit weird in a way I can't describe well. Otherwise, it works well for my use cases but I had to switch back because of this. Also, I needed to check "Prefer Dark Mode" to get a dark mode in libadwaita (I have Adwaita-dark set as my GTK theme), that might just be the expected behaviour and the theming system might be a little different in libadwaita, I didn't look into it. |
I believe there was an issue report related to this for GTK 4. I'll have to check if there's a workaround, but the long-term solution is to stop using the unmaintained GtkTreeView widget in favor of GtkColumnView.
Libadwaita uses a new Freedesktop color scheme spec, which is only available in recent GNOME and KDE releases afaik. |
@AtticFinder65536 I came up with a workaround for the scrolling issue in 92f9859 |
Upstream fix submitted in https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4940 Edit: the fix will be included in GTK 4.6.7 |
The new tray icon implementation compatible with GTK 4 is done. I've also done some work in the past two months to fix a few bugs in GTK 4, and we've almost reached parity with GTK 3! Things left to do before we can consider making the GTK 4 version of Nicotine+ the default:
|
Interacting with the Windows API poses complicated security implications that increase the attack surface of the program, a direct implementation from the core would not be justifiable for a non-essential feature in my opinion. I believe it is (was?) best practice for Windows applications to package a separate tray icon applet executable which runs as a separate process. Often these serve(d) as a launcher type arrangement which is capable of nothing more than spawning/activating the main process and allowing only a limited subset of defined signals from it, in order to avoid having the main process be the host for the applet. |
Do you have any concrete examples? I don't see how a tray icon with a simple menu and a few callbacks could cause many issues. In any case, the notification bubbles currently depend on the tray icon, so it will probably have to remain in the core: nicotine-plus/pynicotine/gtkgui/widgets/notifications.py Lines 133 to 208 in e98a3a5
I haven't explored alternatives for implementing a tray icon on Windows yet, though, so it's all up in the air right now. |
Nothing specific. Reading any of the Windows security updates KB's gives an idea of the scale of the problem.
|
Is the following error related to
|
If the action which leads to the error is as described in #2539 , then yes. |
@critkitten What did you do to get the error? |
For lack of a better place to write this, I plan on supporting GTK 3 for about two more years, possibly three depending on how much demand there is once we reach that point. |
Ubuntu 22.04 (LTS) is finally upgrading from GTK 4.6.6 to 4.6.9, so I'm going to support GTK 4.6.9 in Nicotine+ once again (assuming we don't run into major issues that require 4.8). |
Once https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6052 is merged and a new GTK release is tagged, our GTK 4 Windows builds should be on par with GTK 3 (i.e. no longer blocking a Nicotine+ 3.3.0 release). macOS has not been tested to the same extent yet, I need to reserve time for that. |
Regarding the spell checking, you can use libspelling as an alternative to gspell. |
libspelling needs to support GtkEntry/GtkEntryBuffer first (currently it only supports GtkTextView). |
A bunch of issues were recently fixed in GTK (and Nicotine+ 3.3.3rc2 as a result):
|
@mathiascode @slook - Been away for a while, just wondering how things are progressing with the GTK4 TreeView issues? Thanks for all the work you do! 🥇 --- DS |
Work on porting to Gtk.ColumnView hasn't started yet. Right now we're only doing bug fixes for Nicotine+ 3.3.x to get it in great shape, development on 3.4.x will start sometime later this year. |
@mathiascode In Alpine linux, i get theses errors with KDE 6
XFCE
|
Perhaps try installing the |
Works nicely on KDE 6, The GUI opens up fine however there is a warning.
~ $ nicotine
My Alpine Linux APKBUILD file for 3.3.4 as the default is still 3.3.2. |
Note: Upstream reports need minimal reproducers, e.g. instructions for reproducing the issue in gtk-demo/gtk-widget-factory, or a small .ui file or Python application
General Issues
GTK 4
Windows-specific Issues
Deprecations
Uncertain Future
The text was updated successfully, but these errors were encountered: