Martin Baxter wrote:
I don't find custom properties are very convenient for storing
arrays. Is everyone else using custom property sets for this ?
An overview of using custom props as array storage:
http://lists.runrev.com/pipermail/use-revolution/2002-July/006149.html
--
Richard Gaskin
Fourth
The thing about globals in rev is that they're not really globals
but, in old basic parlance commons. If it was global you would
define it as global and it would be everywhere in Rev without further
global statements inside objects.
--
On the first day, God created the heavens and the Earth
On
Mikey-
Thursday, March 31, 2005, 6:00:06 AM, you wrote:
M The thing about globals in rev is that they're not really globals
M but, in old basic parlance commons. If it was global you would
M define it as global and it would be everywhere in Rev without further
M global statements inside
I think the solution is always to define globals at the script level
rather than the handler. There are good arguments for avoiding them
altogether and I'm finding custom properties more flexible and useful
in many cases where globals used to be my knee-jerk reaction, but one
need not avoid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When would you have to use a global variable, in so far as something
cannot be accomplished with a custom property?
On Mar 31, 2005, at 12:41 PM, Mark Wieder wrote:
Mikey-
Thursday, March 31, 2005, 6:00:06 AM, you wrote:
M The thing about globals in
When would you have to use a global variable, in so far as something
cannot be accomplished with a custom property?
Obviously you don't have to since you can use custom properties, but
you also don't really need to use custom properties because there are
globals...err...commons (I know, I know,
The variable watcher works with globals and locals but not with custom
props. Now if I had a multi custom prop viewer (not the inspector
single view upon selection type) that also worked with globals and
variables.
Tom
On Mar 31, 2005, at 1:18 PM, Frank D. Engel, Jr. wrote:
-BEGIN PGP
Good point, Thomas. I hadn't considered that.
On Mar 31, 2005, at 10:55 AM, Thomas McGrath III wrote:
The variable watcher works with globals and locals but not with custom
props.
~~
Dan Shafer, Co-Chair
RevConWest '05
June 17-18, 2005, Monterey, California
I don't think one ever *has to* use a global. Custom properties will,
as far as I can tell, always do the job just fine.
But:
(a) custom properties take a bit more work to set up (longer syntax
and/or through the inspector)
(b) put hello into gVariableName is shorter and therefore less
On 3/31/05 12:55 PM, Thomas McGrath III [EMAIL PROTECTED] wrote:
The variable watcher works with globals and locals but not with custom
props.
And not with contstants either, I'm afraid...
Ken Ray
Sons of Thunder Software
Web site: http://www.sonsothunder.com/
Email: [EMAIL PROTECTED]
On 3/31/05 1:12 PM, Dan Shafer [EMAIL PROTECTED] wrote:
Other than that, I can't think of any reason not to use custom
properties exclusively.
Well, one is that custom properties can be saved with stacks, and therfore
hold persistent data, whereas globals disappear as soon as the application
This is my experience too. I use globals when I am passing info from
one action to another but I use CPs when an object is involved in the
action.
On Mar 31, 2005, at 2:29 PM, Ken Ray wrote:
However with that said, I use a mixture of globals and custom
properties and
I'm migrating more of my
Frank D. Engel, Jr. wrote:
When would you have to use a global variable, in so far as something
cannot be accomplished with a custom property?
You wouldn't have to use a global, but you may choose to for performance.
Simple operation on a global : 20 ms
Same thing on a custom prop : 3324 ms
On Mar 31, 2005, at 11:29 AM, Ken Ray wrote:
However with that said, I use a mixture of globals and custom
properties and
I'm migrating more of my global use to custom properties as time goes
on...
Another method that you can use rather than globals or custom props is
a state library stack. I
Thomas-
Thursday, March 31, 2005, 12:16:35 PM, you wrote:
TMI This is my experience too. I use globals when I am passing info from
TMI one action to another but I use CPs when an object is involved in the
TMI action.
Wherever possible I pass parameters as arguments to functions in order
to
When would you have to use a global variable, in so far as something
cannot be accomplished with a custom property?
On Mar 31, 2005, at 12:41 PM, Mark Wieder wrote:
Well, I don't find custom properties are very convenient for storing
arrays. Is everyone else using custom property sets for this
Frank D. Engel, Jr. wrote:
When would you have to use a global variable, in so far as something
cannot be accomplished with a custom property?
When you don't want to create an object simply to hold a custom
property. For example, if I'm making a quiz to use with students,
I keep their score
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I generally use the stack for that sort of thing...
Saves me the trouble of creating an extra object, and it's readily
visible from every control on card.
On Mar 31, 2005, at 4:25 PM, Marty Billingsley wrote:
Frank D. Engel, Jr. wrote:
When would you
How do you make a variable global so that you can use it though out the program?
Thanks
Kevin
___
use-revolution mailing list
use-revolution@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution
Just precede its name with the word global:
global gMyVariable, gMyOtherVariable
(The g before the name is not required, but it is considered an
optional best practice because it makes it easier to remember which
variables are global when you use them in your programs.)
You can put this
Thanks for the tip.
I was just fooling around with the socket functions, the problem that
I am having is the only way I can think of sending text from the open
socket is to put it in to a variable and put the contents of the
variable in to txtScreen field. Only problem with that is the the
21 matches
Mail list logo
