[RBASE-L] - Re: RECALC causing all images to blink

[Michael J. Sinclair, MD]

I agree with you analysis. Even so, the developer could use separate variables for each object. Also, even if Rbase still needed to "look at" each _expression_" to determine dependencies, I don't see why the objects that are not dependent have to be redisplayed.

Mike

-------------- Original message from "Emmitt Dove" <emmitt.w.d...@comcast.net>: --------------

The challenge in being able to recalc just one variable is what to do about dependent variables?

 

In forms and reports both you can define expressions that use the results of previously-defined expressions.  If you were to be permitted to order a recalc of just one of those expressions, any expressions farther down in the list that use that result now have invalid values.  So, do these dependent expressions also have to get recalculated?  I think so.  But how does R:BASE determine the dependencies?  By going down the list and only recalculating the ones that reference the variable you ordered to be recalculated?

 

I’m not suggesting it cannot be done, just that it is more complex an issue than it might initially appear.

 

Emmitt Dove

Manager, Converting Applications Development

Evergreen Packaging, Inc.

emmitt.d...@everpack.com

(203) 214-5683 m

(203) 643-8022 o

(203) 643-8086 f

emmitt.w.d...@comcast.net

 

From: rbase-l@rbase.com [mailto:rbas...@rbase.com] On Behalf Of Michael J. Sinclair, MD
Sent: Thursday, March 26, 2009 3:29 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: RECALC causing all images to blink

 

I don't think the Property and Getproperty functions will cause the form to update the displayed objects, they would just change the values. Having a RECALC that would effect a single object or defined set of objects would be very useful.

Mike

-------------- Original message from "Wills, Steve" <jswi...@utmem.edu>: --------------

I could be wrong about this, but I think it might have been possible to do that in a previous version.  I don’t have any “old” doc’s with me here, but the mention of that single-variable/list-of-variables option struck a chord.

 

(Although I don’t perceive it having been so long when I look in the mirror, my first exposure to RBase was v2.11, i.e. a long time ago, so some things, such as statement options, might not be so clear any more!)

 

As for putting it back in to RBase, by request, isn’t that functionality more or less replaced and enhanced by the capabilities of PROPERTY and GETPROPERTY?

 

If so, then perhaps it’s really a request to expose some other Form Control Properties so that RB developers can deliver more bells-n-whistles … or sine qua non’s, as the case may be.

 

 

Steve in Memphis

 

 

From: rbase-l@rbase.com [mailto:rbas...@rbase.com] On Behalf Of mjsmd
Sent: Thursday, March 26, 2009 12:49pm 12:49
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: RECALC causing all images to blink

 

Is it too late to request it?

Michael Sinclair, MD

www.epilution.com

(\__/)

(='.'=)

(")_(")

 

On Mar 26, 2009, at 1:35 PM, karentel...@cs.com wrote:

Boy, I could have sworn that was added at one point, but I don't see mention of it in the help files nor in my notes...  Guess I was wrong!

Karen

Hi Karen,
I just tried that....adding the variable name after the word varilable does not seem to make a difference....it appears that Rbase is just ignoring the variable name. That would be a very nice enahancement. At the moment, adding the variable does not appear to be part of the syntax.
 
Mike