31 Dec
2009
31 Dec
'09
12:34 a.m.
Hi,
The allowNil problem is solved in the latest Glamour-Core:
- allowNil always means that at least one origin port must be notNil
- otherwise, all must be notNil
Cheers,
Doru
On 16 Dec 2009, at 14:30, Johan Fabry wrote:
On 16 Dec 2009, at 07:23, Simon Denier wrote:
--
www.tudorgirba.com
"Obvious things are difficult to teach."
On 15 déc. 2009, at 22:09, Tudor Girba wrote:
This will work OK for now, I can prototype a good-enough user
interface with that. Thanks Doru and Simon!
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hmm, this looks like a strange bug related to
#allowNil. If you
add even the simplest #when: not nil condition (e.g., when: [:cw |
cw notNil]), it works fine. I cannot figure out what the problem
is though.
Meanwhile, a generic condition such as
when: [:one :two | {one. two} anySatisfy: #notNil];
will do the trick
It seems like if all values are nil, something crashes in the
transmission or elsewhere and not restarted