glib | Read-only mirror of https : //gitlab.gnome.org/GNOME/glib

Here is the solution I found :

Changin xvimagesink by ximagesink :

sink = gst_element_factory_make ("xvimagesink", NULL); g_assert(sink);

becomes

sink = gst_element_factory_make ("ximagesink", NULL); g_assert(sink);

Hope it will help some of you facing the same problem.

Meson build here ; basically I have two "executable" target with a shared source, and it seems the first overlap the second for some reason although it should be sequentially.

Example :

I encountered similar problem but with "Microsoft.Print3D" and "Microsoft.DesktopAppInstaller" instead.

IDK xD. It does say in the https://github.com/frida/glib/blob/master/gio/gwin32appinfo.c#L3477 niry posted before, that:

...for 100% correct handling we (GLib and GIO) need to remember which extensions (handlers) support which verbs, and each handler gets its own copy of the verb object, since our design is handler-centric, not verb-centric. The app also gets a list of verbs, but without handlers it would have no idea which verbs can be used with which extensions.

As of why it has no verbs, I suspect it has something to do with registers and installation due to the solution I provided below.

Before you begin, this only fixed my problem with Print3D and made the problem with DesktopAppInstaller worse; it now says "Failed to open manifest..." and I had to reinstall it, which also removes the problem with canvas.

1. Run Powershell with Administrator privilege
2. Get-AppXPackage "HaukeGtze.NotepadEditor" -allusers
3. If it exists, jump to number 4.

or

1. Get-AppXPackage -allusers
2. Find the problematic one (HaukeGtze.NotepadEditor) and note the NAME (not the package full name).
3. Get-AppXPackage [name here] -allusers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

The exact formula to calculate row length is described in the docs for CREATE TABLE. VARCHAR(64) or VARCHAR(35) should not make a difference.

Be aware that rows a stored in data pages in tablespaces. Database systems usually pre-allocate pages for performance reasons. Moreover, pages might not be fully filled or there is compression. And you might have defined indexes which require their own pages with structures. Plus there is metadata in the system catalog.

Input data (for demo purpose, all strings have been cleaned):

A gtk::Window is not the same as a gdk::Window. The former is more like the concept of a "window", while the latter maps better to the concept of X windows. In other display protocols, these are also called "surfaces", which is why it got renamed in GTK 4, also to clear up this confusion.

In any case, to get the underlying surface/window of a widget in GTK, you can call the get_window() method on it (in gtk-rs, this is part of the gtk::WidgetExt trait)

Thanks to @BobMorane who tested the program and found a minor version difference between libraries. It seems that both my source package and his are labeled 2.0.6, but internally there's a minor difference, 1.90.9 and 1.90.11, which was important.

Recompiling with the 1.90.11 version solved the problem!

Checking the Changelog showed no world-shocking differences, but a series of minor compatibility updates. Re-running valgrind did show the disappearance of this message:

I don’t know what your situation is, so this may not be relevant, but here are two points (neither of which actually answers your googlemock question, sorry):

• You may find that g_ascii_string_to_unsigned() is easier to use than g_ascii_strtoll(). It has equivalent functionality for the main use case of parsing the entirety of a string into an integer.
• Functions in GLib are tested in the unit tests for GLib, so you shouldn’t need to write your own duplicate tests. However, if you’ve found a bug in GLib and are testing that, please consider reporting it upstream so everyone can benefit.

As Scheff mentioned in the comments, I forgot that MainWindow::Update needs to return a value of type bool, as that is expected by signal_timeout. Changing the Update method to the following, fixed the issue: