Hi Sharon!
The only thing I'd add or maybe clarify re (B) below is that Replace also serves as Insert (even if not already present), so there's no need to have an 'invalid' component in order to Replace[Insert](invalids) into a field. Nevertheless, as we've both pointed out (to Neil), invalids
An alternative approach would be to use a single field
with multiple data components. That would avoid
transferring 'invalid connections' from one field to
another.
Annotated example attached.
-Ned Piburn
Neil Carlson wrote:
I have two fields (connection dependent data) over the same
Thanks for all the advice on the use of Replace, esp. Sharon;
I know I'll find this useful in the future. I later stumbled
across the solution to my problem: ShowBoundary has a second
tab that that flags whether to use 'invalid' info, and it's
off by default. Turning it on was the solution in
Neil, hope the lengthy discussion doesn't bog you down...maybe ignore for now.
Chris, I welcome further comments... I'll call this my pet topic for '03.
On Jul 3, 7:38am, Chris Pelkie wrote:
Subject: Re: [opendx-users] Include/replace question
Hi Sharon!
The only thing I'd add or maybe
This stuff gets tricky sometimes, because if there are existing 'invalids' some operations, like Replace, may not necessarily cleanly overwrite stuff that is seen as 'invalid'. I would try Remove(invalid connections) followed by Replace(new invalid connections).
On Wednesday, Jul 2, 2003, at
Chris is right about messing with invalids being a tricky process. He gave me
quite useful help long ago. But even now after years of tinkering, I still
stumble across surprising results, things I didn't know, and cases that break
my algorithm (i.e. it was proven to work only most of the time).
