Anonymous user
Talk:GUI enabling/disabling of controls: Difference between revisions
Talk:GUI enabling/disabling of controls (view source)
Revision as of 21:21, 24 August 2010
, 13 years ago→A little convoluted: whitespace
(→A little convoluted: Rule replacement, example purity, observations.) |
m (→A little convoluted: whitespace) |
||
| (3 intermediate revisions by 2 users not shown) | |||
Line 10:
: That's also correct. "Normal" programs would do that, i.e. calling the same enable/disable function once more when the event appears. Again, this would complicate the example even more. I would not mind adding such rules, but is it worth the price of greater complexity in the task's specification? --[[User:Abu|Abu]] 18:11, 23 August 2010 (UTC)
:: This was more a personal observation on platform peculiarities. It's more footnote material than worth making required behavior in a task like this; many Win32 programmers write code that assumes their message queues are more protected than they really are. --[[User:Short Circuit|Michael Mol]] 19:23, 23 August 2010 (UTC)
::: OK. In fact, in case of the proposed PicoLisp solution (also on Win32 under Cygwin) this is not an issue as the +Button component takes care of that --[[User:Abu|Abu]] 05:26, 24 August 2010 (UTC)
:::: It would still be of note for some other languages. Like I said, thought\, it was more an observation than something requiring special attention. -- [[User:Short Circuit|Michael Mol]] 07:46, 24 August 2010 (UTC)
| |||