-
-
Notifications
You must be signed in to change notification settings - Fork 316
Use add_pattern for new dialog's FileFilters
#3828
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
base: main
Are you sure you want to change the base?
Use add_pattern for new dialog's FileFilters
#3828
Conversation
This also updates the screenshots from `data/appstream` to `data/screenshots`.
This also removes the `<developer_name>` tag, as it's deprecated.
This isn't needed anymore.
revert: Duplicated NVIDIA GPUs Fixed by flathub/org.freedesktop.Platform.GL.nvidia#331
appdata: translate=no properties It appears that the appstream project no longer supports `translatable=no` properties, and gettext extract the `translatable=no` marked strings as translatable. I opened an issue to inform about the situation, but `translatable=no` properties are not accepted by developers. You can find the issue here: ximion/appstream#623
…w.py' dialog (bottlesdevs#3730) frontend: Added 'Failed adding to Steam Library dialog' in program_row.py
This is important to have because complex toggles require slightly different parameters. Fixes bottlesdevs#3720
This reverts commit b327ce9.
libportal: Update libportal to 0.9.1 vte: Update vte to 0.79.90 vulkan-headers: Update Vulkan-Headers.git to 1.4.309.0 vulkan-tools: Update Vulkan-Tools.git to 1.4.309.0 ImageMagick: Update ImageMagick to 7.1.1-45 fast_float: Add fast_float
The GtkListBox::row-activated signal only emits when a row is activated, not the child widget. This means, the check button wouldn't trigger the emission of the signal, thereby not updating the NewBottleDialog:selected-environment property. Fixes bottlesdevs#3740
This addresses an issue originally fixed in bottlesdevs#3221 where the GTK function `add_media_type` acted inconsistently across distributions. This was reintroduced in later releases after the UI was updated for creating bottles. As was before, the `add_media_type` function would be the ideal one to use, so this is in actuality a temporary fix.
This addresses code formatting issues discovered during the CI process for this pull request. No functional changes are otherwise present.
|
I see that I can use the package built during CI to verify this functionality! Awesome! I have verified it on my home machine and it continues to work as expected. I shall do a further test on my Steam Deck. |
|
I was able to install this on my Steam Deck and can validate the issue was resolved: I could see "YAML" and "All Files" as options to pick files rather than just "YAML document". I no longer run Ubuntu, however, so any validation on other operating systems would be appreciated. |
Description
This attempts to fix the issue described in #3154 that—although was previously resolved in #3221—has seemingly been reintroduced after the new UI for creating bottles was added.
For context, certain distributions have issues with file choosing dialogs where file types are missing or not correctly handled. This sometimes results in no file types being valid and all file choices becoming invalid. As an example, my main PC correctly shows "YAML" and "All Files" as file type options, but my Steam Deck only shows "YAML documents" (which was not even specified as a name); the former is the most accurate to what the codebase intends. This most noticeable when picking a YAML file for a custom bottle.
The solution proposed here is very similar to the one in #3221: replace the use of
filter.add_mime_typewithfilter.add_pattern. It is not ideal as I recognise the benefit of using the media type, but I believe it is best to ensure consistency until the root cause can be addressed.Fixes #3154
Type of change
How Has This Been Tested?
Warning
I have not done any testing yet! Neither my main PC nor my Steam Deck will let me build this Flatpak, instead resulting in permission denied errors at the very end. I felt it was valuable to provide this implementation early whilst I resolve this in the background.
If anyone feels comfortable validating this in the mean time, I would greatly appreciate it.
Perform and validate the following steps on each of the following: