-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate signals #199
Comments
I'm still undecided about where exactly the signals belong. If they are generated alongside other functions, perhaps Also we should probably fix |
Currently signals trait implemented with bound |
Yeah the |
Other that bound don't see any problem with implementing in |
Generating correct trampoline signatures might require finishing the |
It's worse than that: signal definitions seem to routinely omit <glib:signal name="accel-activate" detailed="1">
...
<parameters>
<parameter name="acceleratable" transfer-ownership="none">
<doc xml:space="preserve">the object on which the accelerator was activated</doc>
<type name="GObject.Object"/>
</parameter>
<parameter name="keyval" transfer-ownership="none">
<doc xml:space="preserve">the accelerator keyval</doc>
<type name="guint" c:type="guint"/>
</parameter>
<parameter name="modifier" transfer-ownership="none">
<doc xml:space="preserve">the modifier combination of the accelerator</doc>
<type name="Gdk.ModifierType"/>
</parameter>
</parameters>
</glib:signal> |
If it omit only for glib-related types then its not big problem |
Speaking of signals, I'm yet again considering adding |
Signals with |
All child issues was closed, so I also close this |
Generate
pub trait xxxSignals
for classes with "IsA" implementation for classes with childrenor direct implimentation for classes without children (same as for "xxxExt" traits).
For both cases generate trampoline function.
Example for ComboBox and TreeSelection: https://github.com/EPashkin/rust-gnome-gtk/tree/signal_sample
The text was updated successfully, but these errors were encountered: