From ea4e6abfdb879c7634fd1bf00220e6f5ab2a45d6 Mon Sep 17 00:00:00 2001 From: Lilith Orion Hafner Date: Thu, 4 Aug 2022 02:59:31 -0500 Subject: [PATCH] Remove outdated accurate warning in docs (#654) --- docs/src/manual/signals.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/src/manual/signals.md b/docs/src/manual/signals.md index 51be5e2c..36227ce9 100644 --- a/docs/src/manual/signals.md +++ b/docs/src/manual/signals.md @@ -83,9 +83,3 @@ id = signal_connect((widget, event) -> cb_buttonpressed(widget, event, guistate, ``` In some situations you may want or need to use an [approach that is more analogous to julia's `@cfunction` callback syntax](../doc/more_signals.md). One advantage of this alternative approach is that, in cases of error, the backtraces are much more informative. - -Warning: it is essential to avoid task switching inside Gtk callbacks, -as this corrupts the Gtk C-stack. For example, use `@async print` or queue a message for yourself. -You can also call `GLib.g_yield()` if you need to block. However, if you are still seeing segfaults in some random method due to there existing a callback that recursively calls the glib main loop (such as making a dialog box) or otherwise causes `g_yield` to be called, wrap the faulting code in `GLib.@sigatom`. This will postpone execution of that code block until it can be run on the proper stack (but will otherwise acts like normal control flow). - -These restrictions should be fixed once https://github.com/JuliaLang/julia/pull/13099 is merged.