- Joined
- Oct 12, 2011
- Messages
- 3,449
I'm working on a multiboard snippet, I would call it singleboard. Since the idea is one multiboard for the whole game. Based on the fact that every player can only see one multiboard at a time (iirc). But it's at cost of "resetting" the multiboard on every display/hide function. Does that worth it?
It's followed by another nice features such as:
- Getting board's cells text/size/icon/color/etc.
Nope, the code isn't ready to be shared yet. I just need your opinion on my question above (1st paragraph). I will post the code here later.
It's followed by another nice features such as:
- Getting board's cells text/size/icon/color/etc.
aboard[1][3].text | get the text at row 1 column 3
aboard[1][3].icon | get the icon at row 1 column 3
- Nice interface. Ease you to work on your multiboard:aboard[1][3].icon | get the icon at row 1 column 3
aboard[1][2].text= | assign a text into a cell (row 1, column 2)
aboard[1][2].icon=
aboard[1][2].style(showText, showIcon) | set a cell's style at row 1, column 2
aboard[1][2].color(r, g, b, a) | set a cell's color
- Desync free: this snippet will preserve all multiboard items in a global variable. Avoiding repeated multiboard item getting and releasing over and over again.aboard[1][2].icon=
aboard[1][2].style(showText, showIcon) | set a cell's style at row 1, column 2
aboard[1][2].color(r, g, b, a) | set a cell's color
Nope, the code isn't ready to be shared yet. I just need your opinion on my question above (1st paragraph). I will post the code here later.