Accessing OnSelected method of Checkbox in a table about ui

[andlabs]

That would be an OnChecked(), but I haven't implemented that yet. I could...

(Are you on Windows, by the way?)

[copiesofcopies]

I'm on Debian/GNOME. I didn't realize it wasn't implemented yet. My problem was that when I tried to access the Checkbox object, I only succeeded in accessing the Enabled bool from the DisplayAccounts struct. Is there a way to access the Checkbox (even though I can't get the method I'm looking for).

[andlabs]

Could you be a little more clear? When the user checks the checkbox, the structure itself is changed for you...

[copiesofcopies]

I understand that ui.NewTable() creates a Checkbox from the Enabled bool in the DisplayAccount struct. What I don't understand is how, in the code, I access the "checked" or "unchecked" value of that Checkbox. I can use the Table's Selected() and OnSelected() methods to see when I particular row is selected, but I do not know how to determine if a Checkbox embedded in a row is checked.

[andlabs]

Oh! You acquire the RLock and examine the boolean field of the structure. The Table code changes that field's value for you.

[copiesofcopies]

Ok, that makes sense. But if I want to call some function when that value changes, I probably need to start a goroutine to watch the bool for changes, right?

[andlabs]

No; I'll need to add an OnChecked() to Table. Will add soon (tomorrow?)

[copiesofcopies]

Thanks for the explanation! Looking forward to having access to OnChecked(), but I'm not in a huge hurry -- I have plenty of other work to do before I need it too badly :)

[andlabs]

Just a quick update: once I finish the newctrl/ stuff I'm going to start doing a rewrite of Table on Windows to use an entirely custom control; once that's feature-complete I can add these features.

[andlabs]

I guess not

First the event system would need to be overhauled to allow passing the checked row and column in. But the current implementation of package ui is already being stretched too thin to be stable. I plan on redoing the backend a third (and hopefully) final time, so I'm not interested in doing any major changes to the backend just yet.

I could add these as methods to Table, but I'd rather not have too many API breaking changes at once. One other thing I want to do is switch to a more generic model interface-based system (with the current struct-based system as an implementation provided by package ui instead). I would need to figure out how this would work with that.

I still need to add this, but we'll see when...

[andlabs]

Replaced with andlabs/libui#310.