J
I guess so, though a filename starting with a tilde (instead of the tilde being somewhere in the middle of the filename) would be quite unlikely… and if there is a tilde and a slash at the beginning, then it's guaranteed to be meant as a path :)
J
This depends on !372 to be merged first. It theoretically fixes a small part of #604, but I have no way to test easily, because Simple Scan is unable to detect any scanner (whether networked or USB) when I run it from GNOME Builder, so it would be nice if someone can confirm whether this works and if it breaks anything in the workflow (in theory it shouldn't).
J
Jeff Fortin (bed3bfc8) at 16 Nov 23:15 app-window: Hide "Save As…" if there's no document ... and 7 more commits
J
I have filed #604 about the sensitive vs visible button state idea, because it turns out to be a problem that affects other buttons as well, so it would be nice if someone were to make a more complete solution for that part.
J
Problem statement One thing that becomes a bit more noticeable when using an explicit label (instead of an icon-only button) for the "Save As…" button to solve #589, is that the button is shown (but insensitive) on startup when the user has not started scanning and there is no document to save, which looks silly and distracts from the more important "Scan" button. However, there is also the situation where the user launches the app without any recognizable scanner detected (ex: no network…
J
I've done the first part, the diff is now simpler; now I'm thinking the 2nd part might benefit from being a separate merge request just to be more careful (I'm wondering if there might be a subtlety beyond just replacing save_button.sensitive by save_button.visible…)
J
Jeff Fortin (f79bbeba) at 16 Nov 22:26 app-window: Relabel "Export" to "Save As…" ... and 3 more commits
J
Weird... the label property really exists, I use it personally in my UI files. Hmm that's interesting, I don't know why I couldn't see it when I looked at that page before. The description for Gtk.Button:label does say "Text of the label inside the button, if the button contains a label widget." though. Maybe the problem is because of the icon-name leftover which conflicts with label? (only one of both can be used at the same time) Oh, I think you're right. I'll try to make a revised commit for…
J
Affected version Nightly flatpak Steps to reproduce Open the event editor (ex: Ctrl+N) Try to choose another calendar for your event What happened Since a few days, the "calendar_combo_row" GcalCalendarComboRow widget in the event editor creates a duplicate preview into the row everytime you select something from its dropdown popover widget: I don't know if it is related, but in the terminal you also get a bunch of such warnings (one per calendar in the comborow's dropdown): Adwaita[ 2]:…
J
This might be gtk#7103, I'm not entirely sure.
J
I guess this might explain the anecdotal issue @tboldt has found with some unicode characters too, like gnome-calendar#1519, in various widgets (I've seen it in Evolution too).
J
Potentially related(?): #3914 where @matthiasc had some ideas and demo code, too.
J
Have you profiled this before and after to be sure (maybe with a backup HDD full of folders/files)? I just remembered issue #2967 (closed), where we previously had some checks for local vs remote directories that ended up being very costly for performance, so back then @antoniof had to nuke them. Just mentioning it here so that we can make sure this is not accidentally reintroducing a problem on this front, or perhaps you had already considered it as part of the new approach :)
J
In the current mainline the setting exists but it is inconsistently applied. Since 2023, it does not actually respect the "sort directories first" setting for search results, which has been a daily pain for me ever since, as mentioned in #2968 (comment 1840850). I think (if I recall correctly) that whenever I asked about it in discussions over the years, Sections were touted as being the solution for this (I'm not sure how exactly). Besides the regression from #2968 (closed), I'm wondering if…
J
It sounds to me like your apps (terminal and text editor) need to implement the required protocol mentioned in #673 (comment 2769412). If so, that's an issue in your apps rather than Mutter, and in that case it's 3. Not GNOME or 3. Not Actionable.
J
I'm not sure the premises of this AI generated ticket are correct. The mainline version of Stamp does not have the calendaring/meeting handling capabilities built-in, you need to be using a special branch for it to work.
J
Feature summary When editing meetings, I would like to add video conference links. How would you like it to work Ideally, you would interface with various APIs (e.g., Zoom). But the simplest way would be to have a preference to register the URL (e.g., to my Zoom personal meeting room), and a button near the map button to fill in. Relevant links, screenshots, screencasts etc. Clicking the camera button fills in the location field with the pre-registered URL.
J
As for the idea of creating a setting for a static URL string: we don't have a preferences dialog in the app, and we will not add one for a single text entry widget. I think the workaround at this point would be to use a memo app (like gnote) to copy from, or a specialized clipboard app (that can retain multiple things), or to tell the videoconferencing system to create the calendar invitation (which is usually how it's done in practice).
J
Thank you very much for digging into that. I was a bit in a rush while filing the ticket, and all I could notice so far was that it broke only with some combinations, and only starting from a certain commit in GNOME Calendar, so I was not entirely sure if it was a GTK issue or something else…
J
OK, retitled for clarity. When it comes to integration: we don't have a plugins system, and I really don't think we will work on integrating external proprietary APIs (and the account management UIs this involves, particularly as GNOME Calendar does not have account management UIs built-in; nor any built-in preference dialog either), unless there is a designed solution for the entire flow and someone comes forward to implement it.
J
Affected version Nightly flatpak main when run through GNOME Builder 51.0 tag when run through GNOME Builder Note that this does not happen when running the 51.0 release from Flathub or from Fedora's RPM repositories. Steps to reproduce Launch GNOME Calendar Nightly or through GNOME Builder Ctrl+N to open the event editing dialog Press Alt on the keyboard (as it is used for mnemonics) What happened Instant crash with: GcalSummarySection-LOG-0x100: 09:55:25.841: EXIT:…
J
We already have Ctrl+S (and language-dependent mnemonics, like Alt+S). Is Ctrl+Enter really a standard keyboard shortcut for this? Where is it documented?
J
What "pre-registered URL"? If you mean something that is in the description (notes) section, GNOME Calendar already auto-detects those and surfaces them in the event summary popover widget with a "Join" button.
J
Until version 51, I was forced to spend my time window-managing Nautilus for no good reason, and I hated every single minute of it. The previous behavior was a focus-scattering, performance-wasting and time-wasting nightmare. For me, being forced to manage a bunch of windows' orphan tabs and duplicate tabs, with the tons of downsides listed below, was definitely a set of distractions making me lose my context. If we wanted to have a bunch of file manager windows scattered across the desktop as…
J
As long as you don't revert to the old behavior by default. What #1687 (closed) solves is me ending up with a million open Nautilus windows (often with duplicate open folders) across every workspace and it becomes total "Shit Work" to manage, particularly for the many people who don't open multiple Nautilus windows. If you don't want your workspace to be switched upon raising/activating the existing window, then I think you have two workarounds: Move Nautilus to your current workspace, or;…
J
Affected version Flatpak version 50.0 from Flathub Logs user@device: $ flatpak run org.gnome.Showtime DEBUG: showtime:54 Starting org.gnome.Showtime v50.0 (release) DEBUG: showtime:55 Python version: 3.13.14 (main, Nov 10 2011, 15:00:00) \[GCC 15.2.0\] DEBUG: showtime:56 GStreamer version: 1.26.11.0 DEBUG: showtime:312 Playing video: file:///run/user/1000/doc/WcSF5wkLQMhI_enGAWN4jw/S01E01.mkv DEBUG: showtime:360 Video paused DEBUG: showtime:355 Video unpaused DEBUG: showtime:319 No previous…
J
Affected version Distribution, including version (example: "Ubuntu 20.04"): Fedora 44 showtime version (example: "45.1"): 50.0 Flatpak is the only package format we support. If you are using a different packaging format please instead report to its respective package maintainer. Is the issue reproducible with our Flatpak package: Description Feature request: I have to watch 60 videos of 5 min each and I want to watch them on 1.5x speed. As it is right now, I have to set the 1.5x speed for each…
J
Whenever you're watching a video on Showtime, and open a second video, it opens in a new window. This results in two videos at the same time, which doesn't seem to be the best possible result.
J
Edited my comment above, and retitled the ticket to talk about the problem/symptom rather than a specific solution. I think with my updated recommendations above, this ought to be reopened for consideration. One solution is to nuke this "feature" and delegate comparison work to specialized apps, the other set of solutions are about making it a secondary workflow or mitigating the symptoms.
J
Description: When a video is playing in Showtime and I open another video from Files, a new Showtime window opens and both videos play at the same time. They keep running until I close one manually. Expected behaviour: The newly opened video plays, and the earlier one stops or is replaced in the same window. Optionally, a preference “Open each video in a new window” for people who want the current behaviour. Steps to reproduce: Open video A from Files so it plays in Showtime. While it’s…