headers
Joe Lewis Wilkins | 8 Oct 02:12

3.0 Field numbering messed up

Attention:

I'm doing some math on a form. Carefully, I thought, I numbered the  
various flds so that I could refer to them in sequence or, at least,  
know what their names are by their positions without having to  
constantly check them out. However, when it came time to refer to them  
I was a bit mistaken. It seems that a field fld "1" does not return  
the value that is in that field; it returns the value that is in a  
totally different field, but the one that is "1" by layering. It was  
the first field I created. It does the same with fld "2"; refers to  
the second field I created and one that is "2" by layering; not by  
name. To me this is a bug. Correct?

I can diddle around and make this work, but I shouldn't have to. When  
I refer to an object by its name I should get the contents of that  
object.

TIA,

Joe Wilkins

_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Permalink | Reply |
headers
Mark Schonewille | 8 Oct 02:29
Gravatar

Re: 3.0 Field numbering messed up

Hi Joe,

Are you using "1", "2" etc. as field names? That's wrong. Revolution  
parses these names as numbers, regardless of the quotes. You must add  
some characters to make sure that Revolution parses the name as a  
string, e.g. "Val 1", "Val 2", etc.

You can refer to these fields in a repeat loop or other script like  
this:

repeat with x = 3 to 7
   add fld ("Val" && x) to myTotal
end repeat
-- do something with myTotal here

I think that saying "I shouldn't have to" is a little inappropriate in  
this particular case, even though it might apply to many other  
workarounds.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum/

Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html
(Continue reading)

Permalink | Reply |
headers
Joe Lewis Wilkins | 8 Oct 02:57

Re: 3.0 Field numbering messed up

Hi Mark,

And thanks. I kind of suspected that was probably the case, but we all  
like to save keystrokes when we can; particularly when there are a lot  
of them. Incidentally, the pointer tooltips plug-in 2.0 that Chipp  
recently released provides the field names as I had designed them "1",  
"2", etc. and no where does anything lead one to suspect that Rev is  
parsing these names as "layer" numbers. Though I can, obviously,  
accept things as they are, in my opinion Rev is dead wrong. Must be  
some backward compatibility issue with MetaCard; but not liking the  
prospect of changing the names for a whole bunch of fields; guess I'll  
just add an "x" in front of each one.

Joe Wilkins

On Oct 7, 2008, at 5:29 PM, Mark Schonewille wrote:

> Hi Joe,
>
> Are you using "1", "2" etc. as field names? That's wrong. Revolution  
> parses these names as numbers, regardless of the quotes. You must  
> add some characters to make sure that Revolution parses the name as  
> a string, e.g. "Val 1", "Val 2", etc.
>
> You can refer to these fields in a repeat loop or other script like  
> this:
>
> repeat with x = 3 to 7
>  add fld ("Val" && x) to myTotal
> end repeat
(Continue reading)

Permalink | Reply |
headers
Scott Rossi | 8 Oct 03:03
Favicon

Re: 3.0 Field numbering messed up

Recently, Joe Lewis Wilkins wrote:

> I kind of suspected that was probably the case, but we all
> like to save keystrokes when we can; particularly when there are a lot
> of them. Incidentally, the pointer tooltips plug-in 2.0 that Chipp
> recently released provides the field names as I had designed them "1",
> "2", etc. and no where does anything lead one to suspect that Rev is
> parsing these names as "layer" numbers. Though I can, obviously,
> accept things as they are, in my opinion Rev is dead wrong. Must be
> some backward compatibility issue with MetaCard; but not liking the
> prospect of changing the names for a whole bunch of fields; guess I'll
> just add an "x" in front of each one.

Joe -- it's not a backward compatibility issue, it's an ambiguity issue.  If
you say "field 1" in your scripts, Revolution has no way to know whether you
mean the first field on the card, or the field named "1", which could really
be the fifth field.  This is why you should use non-numeric-only names as
Mark suggested.

Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design

_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
(Continue reading)

Permalink | Reply |
headers
Joe Lewis Wilkins | 8 Oct 03:19

Re: 3.0 Field numbering messed up

Scott,

I understand; just feeling a bit argumentative this morning. Wrong  
side of the bed? (smile)

Thanks,

Joe Wilkins

On Oct 7, 2008, at 6:03 PM, Scott Rossi wrote:

> Joe -- it's not a backward compatibility issue, it's an ambiguity  
> issue.  If
> you say "field 1" in your scripts, Revolution has no way to know  
> whether you
> mean the first field on the card, or the field named "1", which  
> could really
> be the fifth field.  This is why you should use non-numeric-only  
> names as
> Mark suggested.
>
> Regards,
>
> Scott Rossi

_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
(Continue reading)

Permalink | Reply |
headers
John Tregea | 8 Oct 03:36

Scrolling stack windows?

Hello again fellow Revolutionaries : )

I have built an interface where users can keep on adding new layers of
information down a stack window by clicking a button at the bottom of the
bottom most layer (the button clones the last group and re-populates the
fields to suit the new context).

Because the users frequently want to display 6 or 7 layers one below the
other they quickly run out of screen space.

I believe there are no scrollbars that I can turn on in the stack window
like I can on a text field? I hope I am wrong? But if I am correct can
anyone point me to examples of scrollbars being used to scroll multiple
groups within a window?

Regards

John Tregea

_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Permalink | Reply |
headers
Mark Schonewille | 8 Oct 09:32
Gravatar

Re: Scrolling stack windows?

Hi John,

Group all objects and set the rect of this new group to the rect of  
the card (you may need to make adjustemnts if you have a menubar). Set  
the hScrollba, vScrollbar and the lockLoc of the group to true. Now  
you have something that's very close to a scrolling window.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum/

Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html 
  for more info.

On 8 okt 2008, at 03:36, John Tregea wrote:

> Hello again fellow Revolutionaries : )
>
> I have built an interface where users can keep on adding new layers of
> information down a stack window by clicking a button at the bottom  
> of the
> bottom most layer (the button clones the last group and re-populates  
> the
> fields to suit the new context).
(Continue reading)

Permalink | Reply |
headers
John Tregea | 8 Oct 11:08

RE: Scrolling stack windows?

Dear Mark,

Thanks for that. I think I would have to ungroup the existing top level
group then select whatever number of clones groups the user is displaying
and regroup them. Or is there a way of cloning into a group the way I can
copy into a card?

Thanks and regards

John

-----Original Message-----
From: use-revolution-bounces@...
[mailto:use-revolution-bounces@...] On Behalf Of Mark
Schonewille
Sent: Wednesday, 8 October 2008 6:32 PM
To: How to use Revolution
Subject: Re: Scrolling stack windows?

Hi John,

Group all objects and set the rect of this new group to the rect of  
the card (you may need to make adjustemnts if you have a menubar). Set  
the hScrollba, vScrollbar and the lockLoc of the group to true. Now  
you have something that's very close to a scrolling window.

--
Best regards,

Mark Schonewille
(Continue reading)

Permalink | Reply |
headers
Chipp Walters | 8 Oct 11:32

Re: Scrolling stack windows?

copy button 1 to group 1

It works.

On Wed, Oct 8, 2008 at 4:08 AM, John Tregea <john@...> wrote:

> Or is there a way of cloning into a group the way I can
> copy into a card?
_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Permalink | Reply |
headers
John Tregea | 8 Oct 12:00

RE: Scrolling stack windows?

Great news. Thanks

-----Original Message-----
From: use-revolution-bounces@...
[mailto:use-revolution-bounces@...] On Behalf Of Chipp Walters
Sent: Wednesday, 8 October 2008 8:32 PM
To: How to use Revolution
Subject: Re: Scrolling stack windows?

copy button 1 to group 1

It works.

On Wed, Oct 8, 2008 at 4:08 AM, John Tregea <john@...> wrote:

> Or is there a way of cloning into a group the way I can
> copy into a card?
_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
(Continue reading)

Permalink | Reply |
headers
Thomas McGrath III | 8 Oct 03:23
Favicon

Re: 3.0 Field numbering messed up

Joe,

This will add the X in one shot before each field for you.

on mouseUp pMouseBtnNo
     repeat with x = 1 to the number of fields of card 1
         set the  name of fld x to ( "X" & x)
     end repeat
end mouseUp

It might be easier to think of 1 and "1" as reserved words in this  
instance.

HTHs

Tom McGrath III

On Oct 7, 2008, at 8:57 PM, Joe Lewis Wilkins wrote:

> Hi Mark,
>
> And thanks. I kind of suspected that was probably the case, but we  
> all like to save keystrokes when we can; particularly when there are  
> a lot of them. Incidentally, the pointer tooltips plug-in 2.0 that  
> Chipp recently released provides the field names as I had designed  
> them "1", "2", etc. and no where does anything lead one to suspect  
> that Rev is parsing these names as "layer" numbers. Though I can,  
> obviously, accept things as they are, in my opinion Rev is dead  
> wrong. Must be some backward compatibility issue with MetaCard; but  
> not liking the prospect of changing the names for a whole bunch of
(Continue reading)

Permalink | Reply |
headers
Joe Lewis Wilkins | 8 Oct 03:25

Re: 3.0 Field numbering messed up

Tom,

Boy! Today IS a slow one. (smile)

Thanks,

Joe Wilkins

On Oct 7, 2008, at 6:23 PM, Thomas McGrath III wrote:

> Joe,
>
> This will add the X in one shot before each field for you.
>
> on mouseUp pMouseBtnNo
>    repeat with x = 1 to the number of fields of card 1
>        set the  name of fld x to ( "X" & x)
>    end repeat
> end mouseUp
>
>
> It might be easier to think of 1 and "1" as reserved words in this  
> instance.
>
> HTHs
>
> Tom McGrath III

_______________________________________________
use-revolution mailing list
(Continue reading)

Permalink | Reply |
headers
Jim Ault | 8 Oct 03:17
Favicon

Re: 3.0 Field numbering messed up

On 10/7/08 5:16 PM, "Joe Lewis Wilkins" <pepetoo@...> wrote:

> Attention:
> 
> I'm doing some math on a form. Carefully, I thought, I numbered the
> various flds so that I could refer to them in sequence or, at least,
> know what their names are by their positions without having to
> constantly check them out. However, when it came time to refer to them
> I was a bit mistaken. It seems that a field fld "1" does not return
> the value that is in that field; it returns the value that is in a
> totally different field, but the one that is "1" by layering. It was
> the first field I created. It does the same with fld "2"; refers to
> the second field I created and one that is "2" by layering; not by
> name. To me this is a bug. Correct?
> 
> I can diddle around and make this work, but I shouldn't have to. When
> I refer to an object by its name I should get the contents of that
> object.
> 
Referring to objects using numbers as labels is a risky practice since Rev
will resolve numbers to mean the position in the order of fields, buttons,
other objects.
 (1 to the number of fields, regardless of layer number, but in the layer
'order').
--------- Reset the names of all the fields
on setNameOfFields
  repeat with x = 1 to the number of fields
    put word 1 of the short name of field x into NM
    if NM is a number then  --  only touches number-style fields
       set the name of field x to NM & " F"
(Continue reading)

Permalink | Reply |
headers
Joe Lewis Wilkins | 8 Oct 03:23

Re: 3.0 Field numbering messed up

Jim,

Thanks for the routine. I had already done something similar. It  
wasn't that big a deal. As I said, wrong side of the bed. Or my  
arthritis!

Joe Wilkins

On Oct 7, 2008, at 6:17 PM, Jim Ault wrote:

> Referring to objects using numbers as labels is a risky practice  
> since Rev
> will resolve numbers to mean the position in the order of fields,  
> buttons,
> other objects.
> (1 to the number of fields, regardless of layer number, but in the  
> layer
> 'order').
> --------- Reset the names of all the fields
> on setNameOfFields
>  repeat with x = 1 to the number of fields
>    put word 1 of the short name of field x into NM
>    if NM is a number then  --  only touches number-style fields
>       set the name of field x to NM & " F"
>    end if
>  end repeat
> end setNameOfFields

_______________________________________________
use-revolution mailing list
(Continue reading)

Permalink | Reply |

Gmane