desktop.Remove(widget) & Widget remains on screen, becomes unresponsive about sfgui HOT 5 CLOSED

Don't remove the widget when your are inside the signal handler. This will lead to undefined behaviour. Remember what you have to remove and remove it after your call to HandleEvent() returns.

from sfgui.

Is there an example available that shows how to do this? (Desktop.cpp seems to 'remove' inside the signal handler, unless I'm misunderstanding the terminology?)

from sfgui.

In the case of Desktop.cpp, we first create another shared_ptr to the widget we want to remove, remove it and return from the handler. We also make sure not to try to manipulate the object too much. Once we remove it we must assume it is no longer safe to access. The example was written this way to stay short, and given its simplicity we could also manage the dangers that are associated with this method. We wouldn't recommend doing this in anything more complex than this scenario however.

from sfgui.

Sorry to bother you again, but what do you mean by "Remember what you have to remove and remove it after your call to HandleEvent() returns."?

Does this mean storing the widget to be removed inside of a class or global variable and then deleting it inside of the while (mainWindow.pollEvent(event)) code block?

from sfgui.

Does this mean storing the widget to be removed inside of a class or global variable and then deleting it inside of the while (mainWindow.pollEvent(event)) code block?

Yes.

from sfgui.