How to make sure GC allocated resources stay around when used in C functions?

[Kagamin via Digitalmars-d-learn]

On Tuesday, 13 May 2014 at 18:47:45 UTC, Gary Willoughby wrote:
> They are not bound automatically but may be bound later.

So they will be allocated on demand - only if it's bound, Args 
will be allocated, so widget will have only one Args allocated, 
or as many as were actually bound. Or do you want to save on one 
pointer per widget?

Keyboard shortcuts are probably rare too, widgets should handle 
most common shortcuts like text editing or copying on their own 
without special handling by the user program, right?