You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Gtk::TextBuffer#selection_content returns a Gdk::ContentProvider object, this object can return its contents wrapped in a GValue, however the called must initialize the GValue to the right type before calling Gdk::ContentProvider#value, otherwise an error is thrown when e.g. a call for #as_s is done in the returned GValue:
Unhandled exception: Cannot obtain raw value for g_type 0 (ArgumentError)
from lib/gi-crystal/src/bindings/g_object/value.cr:113:9 in 'raw'
from lib/gi-crystal/src/bindings/g_object/value.cr:120:7 in 'raw'
from lib/gi-crystal/src/bindings/g_object/value.cr:123:5 in 'as_s'
Current Gdk::ContentProvider#value generated binding implementation:
defvalue : GObject::Value# gdk_content_provider_get_value: (Method | Throws)# @value: (out) (caller-allocates)# Returns: (transfer none)
_error =Pointer(LibGLib::Error).null
# Generator::CallerAllocatesPlan
value =GObject::Value.new
# C call
_retval =LibGdk.gdk_content_provider_get_value(to_unsafe, value, pointerof(_error))
# Error checkGdk.raise_gerror(_error) unless _error.null?
# Return value handling
value
end
Note that the return value is also lost... i.e. I need to decide what to do with the tons of out values the GTK API has.
The text was updated successfully, but these errors were encountered:
Using
Gtk::TextBuffer#selection_content
returns aGdk::ContentProvider
object, this object can return its contents wrapped in a GValue, however the called must initialize the GValue to the right type before callingGdk::ContentProvider#value
, otherwise an error is thrown when e.g. a call for#as_s
is done in the returned GValue:Current Gdk::ContentProvider#value generated binding implementation:
Note that the return value is also lost... i.e. I need to decide what to do with the tons of out values the GTK API has.
The text was updated successfully, but these errors were encountered: