StefanSalewski

Thinking more about it, a small async, threading or GUI example would be nice for features page too.

Well, should be fixed, try ``` nimble uninstall gintro nimble install gintro@#head ```

Note that we should generally not use casts, the 00 types or access the .impl fields directly when we use the gintro bindings. The examples in the README and in...

OK, now I understand: The ForEach() should have a callback proc as parameter, which is called from GTK directly. In that case we have to create a Nim macro, similar...

>I might be interested in having a go, since Yes, it should be not too difficult. I generally grep one of the existing gintro macros, and just modify it. The...

I was going to start creating the foreach macro. I think the idleAdd() is not a bad starting point, but it will need some serious changes. Unfortunately all of our...

OK, I have the first skeleton foreach() macro already working, after less than 3 hours. IdleAdd() was indeed a fine starting point, and the macro is basically very simple. I...

Well, I assume you have already retired, but I have just added a first try of a foreach macro. Unfortunately it works currently only with ref parameters. I just tried...

And for your source file: ``` Instead of result.addName = cast[Entry](builder.getObject("add_name")) something like result.addName = builder.getEntry("add_name") should work since a few years now. All the callbacks like proc on_add_entry_clicked(widget: Widget,...

OK, this macro version seems to work with strings: ```nim macro foreach*(container: gtk.Container; p: untyped; arg: typed): untyped = var foreachID {.compileTime, global.}: int inc(foreachID) var ats = $getTypeInst(arg).toStrLit let...