2022-10-16 08:07:13 -05:00
|
|
|
package gui
|
|
|
|
|
|
|
|
import "log"
|
|
|
|
|
|
|
|
import "github.com/davecgh/go-spew/spew"
|
|
|
|
|
2022-10-19 13:23:22 -05:00
|
|
|
/*
|
|
|
|
Get the int from the gui toolkit
|
|
|
|
because eventually this gui package should become it's own seperate go routine and never interact from the
|
|
|
|
gui subroutine back into the upstream application using the gui package
|
2022-10-16 08:07:13 -05:00
|
|
|
|
2022-10-19 13:23:22 -05:00
|
|
|
TODO: instead store the int in the Node structure? (this is probably a better idea)
|
|
|
|
because technically every interaction with the toolkit has to go through the Queue() goroutine.
|
|
|
|
Is it "has to go" or "should go"? Probably it makes sense to strictly inforce it. No "callback" functions. IPC only (go channels)
|
|
|
|
*/
|
2022-10-16 08:07:13 -05:00
|
|
|
func (n *Node) Int() int {
|
2022-11-13 08:53:03 -06:00
|
|
|
if (Config.Debug.Toolkit) {
|
2022-10-16 08:07:13 -05:00
|
|
|
log.Println("gui.Node.Int() for node name =", n.Name)
|
|
|
|
scs := spew.ConfigState{MaxDepth: 1}
|
|
|
|
scs.Dump(n)
|
|
|
|
}
|
|
|
|
|
2022-11-13 08:53:03 -06:00
|
|
|
// i := n.toolkit.Value()
|
|
|
|
i := 3333
|
2022-10-16 08:07:13 -05:00
|
|
|
return i
|
|
|
|
}
|
2022-10-19 13:23:22 -05:00
|
|
|
|
|
|
|
// which name to use?
|
|
|
|
func (n *Node) Value() int {
|
|
|
|
return n.Int()
|
|
|
|
}
|
|
|
|
|
|
|
|
func (n *Node) SetValue(i int) {
|
|
|
|
log.Println("gui.SetValue() START")
|
|
|
|
n.Dump()
|
2022-11-13 08:53:03 -06:00
|
|
|
// n.toolkit.SetValue(i)
|
2022-10-19 13:23:22 -05:00
|
|
|
}
|