-
Notifications
You must be signed in to change notification settings - Fork 4
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
GRunLoop references GtkEngine #7
Comments
oops.
yes, of course this has to be GEngine, not GtkEngine :)
…On Feb 1 2022, at 12:56 pm, Martín Dias ***@***.***> wrote:
('GObject-Base' referencing 'Gtk-Base')
This happens in GRunLoop class>>#current:
current
^ GtkEngine current runLoop
I see two possible fixes:
Just replace this method by ^ GEngine current runLoop
Move this current to GtkRunLoop and place a ^ self subclassResponsability in GRunLoop.
@estebanlm (https://github.com/estebanlm) ?
—
Reply to this email directly, view it on GitHub (#7), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAD5MXRL5YQLQI7EAISNWADUY7C5ZANCNFSM5NI5UC6Q).
Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).
You are receiving this because you were mentioned.
|
Note: There is also a reference to the same class from GStructure>>autoRelease |
tinchodias
added a commit
to tinchodias/gtk-bindings
that referenced
this issue
Feb 1, 2022
(Fixes issue pharo-spec#7)
tinchodias
added a commit
to tinchodias/gtk-bindings
that referenced
this issue
Feb 2, 2022
(Fixes issue pharo-spec#7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
('GObject-Base' referencing 'Gtk-Base')
This happens in
GRunLoop class>>#current
:I see two possible fixes:
^ GEngine current runLoop
current
toGtkRunLoop
and place a^ self subclassResponsability
inGRunLoop
.@estebanlm ?
The text was updated successfully, but these errors were encountered: