Talk:Honeycombs: Difference between revisions
I think it'd be best to let the implementer worry about that.
(widgets) |
(I think it'd be best to let the implementer worry about that.) |
||
Line 17:
Maybe we can drop the message, and just keep a record of which hexagons have neen clicked. Depending on how the widgets work for the language, we could either set this as a property of the widget itself, or keep the information in a separate array. We can then use this record to programmatically prevent reacting to already clicked hexagons. I am open to suggestions on the wording here.
: That's something that's probably best left unspecified so that it can be left maximally to the discretion of the implementer. What's significant is that the on-screen and interactive behavior is preserved, right? Let the implementer worry about that. --[[User:Short Circuit|Michael Mol]] 16:45, 26 May 2011 (UTC)
[[User:Markhobley|Markhobley]] 16:37, 26 May 2011 (UTC)
| |||