https://bugs.kde.org/show_bug.cgi?id=509114
--- Comment #7 from [email protected] --- So I'm trying to grep, but how does that work? For Bazzite it uses Clapgrep for a visual of it, and I see it searching them, but where would I find the metadata? It gives a lot of instances of it appearing, and I have no idea what I should be looking for in these entries. There's an entry here that looks like this: <interface name="wp_image_description_creator_params_v1" version="1"> <description summary="holder of image description parameters"> This type of object is used for collecting all the parameters required to create a wp_image_description_v1 object. A complete set of required parameters consists of these properties: - transfer characteristic function (tf) - chromaticities of primaries and white point (primary color volume) The following properties are optional and have a well-defined default if not explicitly set: - primary color volume luminance range - reference white luminance level - mastering display primaries and white point (target color volume) - mastering luminance range The following properties are optional and will be ignored if not explicitly set: - maximum content light level - maximum frame-average light level Each required property must be set exactly once if the client is to create an image description. The set requests verify that a property was not already set. The create request verifies that all required properties are set. There may be several alternative requests for setting each property, and in that case the client must choose one of them. Once all properties have been set, the create request must be used to create the image description object, destroying the creator in the process. </description> <enum name="error"> <description summary="protocol errors"/> <entry name="incomplete_set" value="0" summary="incomplete parameter set"/> <entry name="already_set" value="1" summary="property already set"/> <entry name="unsupported_feature" value="2" summary="request not supported"/> <entry name="invalid_tf" value="3" summary="invalid transfer characteristic"/> <entry name="invalid_primaries_named" value="4" summary="invalid primaries named"/> <entry name="invalid_luminance" value="5" summary="invalid luminance value or range"/> </enum> <request name="create" type="destructor"> <description summary="Create the image description object using params"> Create an image description object based on the parameters previously set on this object. The completeness of the parameter set is verified. If the set is not complete, the protocol error incomplete_set is raised. For the definition of a complete set, see the description of this interface. The protocol error invalid_luminance is raised if any of the following requirements is not met: - When max_cll is set, it must be greater than min L and less or equal to max L of the mastering luminance range. - When max_fall is set, it must be greater than min L and less or equal to max L of the mastering luminance range. - When both max_cll and max_fall are set, max_fall must be less or equal to max_cll. If the particular combination of the parameter set is not supported by the compositor, the resulting image description object shall immediately deliver the wp_image_description_v1.failed event with the 'unsupported' cause. If a valid image description was created from the parameter set, the wp_image_description_v1.ready event will eventually be sent instead. This request destroys the wp_image_description_creator_params_v1 object. The resulting image description object does not allow get_information request. </description> There's a few lines in the grep selection in Clapgrep that says there's an instance where the thing is created, then interface, then destroyed. Idk if this is all what you're trying to find, so lmk. -- You are receiving this mail because: You are watching all bug changes.
