J
Duplicate of #72. Personally, I agree with both of the reports and disagree that being able to play two videos as separate instances/windows, as the default behavior, would somehow be something that people would actually want. Pretty much nobody can realistically listen to multiple videos at the same time. Instead, I would expect either a "New window" action for this (to drag and drop videos into), or I would expect people to use a specialized video comparison app, like I mentioned in #72…
J
Presumably this might fix not only #239 but also #300, #306 and #313… @rmader, does the approach here look correct from the GStreamer perspective?
J
Doesn't that sound impossible with Flatpak then?
J
Summary Opening a video file whose filename contains # (e.g., *test #6.mp4) fails to play with the error message "Failed to pause". Renaming the file to remove # resolves the issue immediately. Steps to reproduce Create a playable MP4 file named test #1.mp4 (or any name containing #). Open GNOME Files (Nautilus) and double-click the file to open it in Showtime (Flatpak). Showtime fails to open the media and displays Failed to pause. Rename the exact same file to test_1.mp4. Double-click again,…
J
I asked Georges whether he has any thoughts on this, and he said, "I'm fine with the idea, but the code needs some love". I do not know in exactly which way, and I do not have opinions on code myself (especially C code). At least you have a greenlight to explore the direction that was discussed above in this thread, I guess!
J
Oh, that's interesting! I couldn't quite tell clearly from @carlosg's comment that you linked to, but further down in that thread I do see this part: […] I agree how the situation you describe can look glitchy, although the most common intent of the notification is precisely to wake up the display after dimming and let the user notice that the system is going to sleep, in case they didn't intend it to. […] So I guess this here would be a 2. Needs Design / 2. RFC if it is to change.
J
I doubt this is happening with any recent versions of GNOME (ex: 51+), right? It could have been fixed by !462 (merged) as part of #903 (closed)?
J
According to the first reply in https://discourse.gnome.org/t/how-to-eliminate-auto-suspend-and-screensaver-enabled-notification/8658, this notification is not treated differently from the other notifications from gnome-settings-daemon's "power" plugin. Out of curiosity, looking through https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commits/main?message=suspend&page_size=100 I was able to find gnome-settings-daemon@0a82672f as the commit that originally introduced that notification back…
J
I don't think this has been happening in any recent versions of GNOME, no? Are you seeing this in 51+ ?
J
Assuming it works with search too, @coreyberla thinks that !2210 might address the architectural problems I had cited in the description above (from a discussion with @antoniof roughly 2½ years ago).
J
A practical consequence of this is that those using Google Calendar as an Epiphany web app, with the "Notifications" permission denied in the web app's settings, will experience the app breaking itself whenever an event reminder notification shows up as a modal GTK alert dialog on the page and remains unacknowledged for 120 seconds, causing WebKitGTK to think it has become unresponsive, so if you leave it unattended it stacks the endless "not responding" dialogs (from #2971 (closed)) on top of…
J
@goop have you noticed anything? If you haven't tried yet, Fedora 45 is out today with GNOME 51.x, so this is readily accessible, in addition to GNOME OS Preview.
J
The result from @ARAKHNID's !887 (merged) works really well, at least in the English version. Here are two videos with Orca announcing the various spinbutton widgets and the month names for each day in the pickers' grid: In the event editor dialog's date pickers In the sidebar's minicalendar In !887 (comment 2915322), @TheEvilSkeleton chose to have it consistently announce the month on every selected day, rather than only when the month changes.
J
We have a similar problem in #1447 too, for the tooltips of the event widgets instead of the accessibility labels of the cells that contain them…
J
Originally filed by @jfft in Bugzilla #774946 I have an un-deletable "Personal" calendar created by Evolution/EDS that I never use. I unchecked it in GNOME Calendar (and EDS)'s settings, but it still shows up among possible calendars when I create/edit an event in GNOME Calendar. It would be nice if it was possible to fully disable it, not just hide it. Calendars list popover - old screenshot Calendars list popover - slightly less old screenshot Quick-add popover, main view Quick-add popover,…
J
As per #88 (comment 2911249) above, there is nothing we can do here other than making the UI clearer through #1117 and #1380. Therefore, I am closing this non-actionable ticket in favor of the two others.
J
Do you really use that for show/hide the events from that calendar in the GUI? […] Oh, you are correct, we actually don't use e_source_set_enabled: a quick git grep source_set_enabled returns nothing in Calendar's codebase, but instead git grep selectable_get_selected and git grep selectable_set_selected returns results in gcal-calendar.c (only), that's how we actually handle the visibility of the calendars. but there is no API to delete the fallback "On This Computer/Personal" source, right?…
J
I have some doubts about the "hide the widget entirely" approach (it would be the same problem with the "Online Accounts" hyperlink int he calendars management dialog, by the way), so I have summarized them here: #1668 (comment 2919969)
J
I am not convinced that hiding the widgets would be the best approach to solve the problems detailed in the comments in #1393 (closed). Hiding the menu item in the main window (and the "Online Accounts" hyperlink in the "Add Remote Calendar…" dialog) would just confuse users more and attract criticism for "not having anything configurable" (which is not technically true), and maintain or increase support load on the bug tracker as we would unfortunately keep having to point people to #1393…
J
I snipped out the AI-generated part of this ticket's description and put it into a collapsed folding section, so that it doesn't overwhelm the reader with what is essentially statistical guesswork.
J
i know there is the button to enable the multiple selection but it would be nice to have also the usual keyboard shortcuts like ctrl or maiusc maybe they could be implemented?
J
don't create a GtkLabel child, instead use the label property of GtkButton That's actually the first thing I tried, and it wouldn't work at all. Only after a lot of headbanging did I end up going through the pain of adding a whole child to it, because it seemed impossible otherwise. If you actually look at https://docs.gtk.org/gtk4/class.Button.html, you can see that GtkButton does not offer a label property; it actually expects you to pack a child label widget into it, or to instantiate it…
J
Maybe one way to solve this would be to have some auto-remembered grouped togglebuttons filters in the searchbar, to let the user choose between: [ Nearest | Most relevant ] …or even: [ Nearby | Within 300 km | Worldwide ] (with the implication that the last two choices are ranked by relevance but still limited to a certain distance for the "Within 300 km" choice)? I think this giving the user control over this would let them get much more relevant results for whatever context they are in,…
J
I've finally tested this again today, and: I think the 1st item is fixed, because it reads it as "From" and "Combobox" but it doesn't read the email address (not entirely sure, because I'm encountering the same issue as GNOME/gnome-calendar#1666) The 2nd item is partially fixed, as it reads them all as "Contact". I filed #249 as a spin-off for that issue. The third item (confirmation dialog) is fixed!
J
Testing the results of #64 (closed) with Orca, when tabbing through the mail composer's various editable text entry widgets, I noticed that it reads the To/CC/BCC fields as "Contact" (because it uses the same blueprint accessibility label for all the stamp-contact-completion widgets), so they cannot be distinguished by blind users. I would expect them to be read: "To", "Carbon copy" (or "Carbon copy to…") and "Black carbon copy" (or "Black carbon copy to…").
J
Interesting, I can also reproduce with @jbrummer's "Stamp" email client, nightly flatpak version, by: Launching orca Launching flatpak run org.tabos.stamp Starting the email message composer (with Ctrl+N) If Orca is already running while you try to do that at step 3, it will crash Stamp, because it selects the "From" combobox (due to jbrummer/stamp#248). If you enable Orca after showing the composer window at step 3, it doesn't crash... until you focus out the "From" combobox widget with Tab…
J
Whenever you call the mail composer dialog through one of the methods below, the "From" selector widget is the one that grabs focus by default: That is not really useful in the vast majority of cases. The "To" text entry, subject line entry, or body should be the ones getting the focus by default, depending on which one is most relevant, so that the user can start typing straight away. Suggested heuristic Here are the scenarios I can think of: On a brand new email message (called via Ctrl+N or…
J
Well, this is already an improvement, and I can see that it works well in practice (including the dynamic showing of the labels depending on the available space), thank you! I really think the "Send" and "Add Attachment" composer buttons, which are going to be the most-used ones, deserve to have explicit labels as well. Currently, it is not possible at all for a non-technical user to know how to actually send the email, this button doesn't say anything: The lack of a clearly labelled "New…