Though, from a philosophical standpoint, I'd rather have UI be on a widget so that the player can freely swap UI. Which I never do, cause doing a synced gadget -> unsynced gadget is much simpler to me than writing whatever's needed for gadget to expose stuff to widgets.t synced gadget -> widget, and also I pefer having all the code related to the same stuff in the same file.
That's what I did. At first it seemed convoluted, but anyway there was no other way, and in the end it's only a couple lines of codes. The annoying bit is that I cannot forbid the user to switch off the widget.Forboding Angel wrote:Couldn't you just have a widget that acts as a go-between for I/O? That being it's only function. It strikes me that it should be simple enough to pass parameters to the widget and then make the widget do it's thing.
