Hugo Parente Lima
Hugo Parente Lima
No, keep it open, the bug still exists. Even the fix need to be made on gi-crystal, IMO is ok the bug to be filed here since it's a bug...
I just pushed these changes while this isn't proper fixed in gi-crystal. They will be available in next release.
I see, it's another issue from the fact that GI-Crystal just ignore the _out_ parameters. It's on my queue to touch this on GI-Crystal and let every method that have...
Yes, what the binding generator uses this user_data pointer to pass a Crystal `::Box` object with the closure, so you can pass a Crystal callback for it. All these `_async`...
Hi, it's a known issue. The API is generated from source files generated by the binding generator, so they aren't on github. If you look at the links you will...
Yes, a PR is welcome.
for each module there's a `Abstract` class, e.g. `Gio::AbstractAsyncResult`, but they exist to be used as return value for GTK functions that returns interfaces (i.e. Crystal modules). Anyway, I didn't...
I think will be useful to link this tutorial on this shard README and on gi-crystal README as well.
The PR above add support for `_async` functions, however a lot of `_finish` functions uses out parameters and out parameters still not fully implemented in GICrystal... I think now I...
Here´s a monkey patch I did to be able to use `GtkSource::FileSaver#save_async` from GTKSourceView. ```Crystal module GtkSource class FileSaver def save_async(io_priority : GLib::Priority, cancellable : Gio::Cancellable? = nil, &callback :...