[REBOL] Re: Checkbox state is not changing - maybe Allen Kamp updates his View
From: geza67:freestart:hu at: 6-Sep-2001 22:34
> Just be aware that you are asking for people to
> do work for you. Although it would benefit all
> of us, not just you, it is still work to prepare
Sorry if my words mislead your mind: _I_ haven't asked anybody for doing
anything. I just waived a flag, gave a notification. It is everybody's
(specifically every " gurus' ") personal issue if he would react and
work for _ME_(?)
REBOL community _painfully_ misses organized documentation. Being a
rather small group and RT being a really small company as well,
optimal "human resource management" is AN issue.
> You might want to send feedback to Allen with this,
Allen updated his FAQ beforehand and contacted me for verifying the
code (which I indeed did): Now his VIEW FAQ is up-to-date upon
>> In /View 1.x where x<>2 but some earlier release, checkbox's 'state
>> property _worked_ as expected. Maybe this /View release is buggy in
>> this respect.
> way. Whether or not you expected it is a matter of religion.
It is not a matter of religion - I think. If something worked one way
in a release and works other way in a more recent release then the
_change_ itself is a bit irritating. MS changed the document format of
MS Office with almost every release making all users mad. WordPerfect
has not changed the WP format for years - besides its typographic
properties were far more advanced "ab ovo". Word just tried to race
behind. If REBOL issues considerable modifications (e.g. look at
'stylize + 'with) in each release of VID then one may really ask: is
the View framework so fallible & inmature that not only behind-the-scenes
operations but the API itself should be reconfigured for each release?
> Allen's old code is now out of date, because of the more
> consistent treatment of the data attribute in the latest View.
I appreciate it.
> Try this, which simulates code that takes a while
> (one second).
> view layout [button [wait 1]]
> So the sequence is:
> - user presses mouse button on button
> - button changes visual state to "down"
> - user releases mouse button over the button
> - button does action block
> - button changes visual state to "up"