This was the biggest problem with the 'science' behind the creation of
the Ribbon. Although they used FITS law to decide placement they
actually misinterpreted FITS law which helps decide the travel
distance between common work flow and buttons, menus, keystrokes, etc.
They (MS) determined
Eric-
I can't remember whether I've posted this here or not, but anyone
interested in the Office ribbon might well enjoy this video talk. It's
some 75 minutes long so prepare to sit for a while, but it's a
fascinating perspective into what the ribbon development tean thought
was right and wrong
Hey List Folks:
I'm having trouble remembering how to get Rev to see object references in
variables, as opposed to the variable data. For example, if I script:
put the long id of field 1 into tField
put the number of lines of tField
I'll get '1' in the message box regardless of how may
On Sep 26, 2008, at 8:22 AM, Scott Rossi wrote:
Hey List Folks:
I'm having trouble remembering how to get Rev to see object
references in
variables, as opposed to the variable data. For example, if I script:
put the long id of field 1 into tField
put the number of lines of tField
I'll
Hey Scott...
put the long id of field 1 into tField
long id of field 1 of stack WHAT?? sometime this stuff needs to be
addressed more clearly for the engine
especially from the message box.
I mess this up all the time. I just assume the engine 'knows' what I want!
Hey List Folks:
I'm
Scott Rossi wrote:
I'm having trouble remembering how to get Rev to see object references in
variables, as opposed to the variable data. For example, if I script:
put the long id of field 1 into tField
put the number of lines of tField
I'll get '1' in the message box regardless of how may
Scott, in the case of a field,
put the long id of fld 1 into tField
put line 1 of the text of tField
seems to work.
Best,
Mark
On 26 Sep 2008, at 07:37, Richard Gaskin wrote:
Scott Rossi wrote:
I'm having trouble remembering how to get Rev to see object
references in
variables, as
Bonjour Scott,
The rule is rather simple when working with long IDs or long names:
You *must* require a property :-)
number of lines of is not strictly a property but number of lines
of the text of is because text is a property but lines is just a
keyword.
Regarding fields, it's a bit
Recently, Richard Gaskin wrote:
I'm having trouble remembering how to get Rev to see object references in
variables, as opposed to the variable data. For example, if I script:
put the long id of field 1 into tField
put the number of lines of tField
I'll get '1' in the message box
Hi Eric,
This reminds me of another interesting shortcut for use with send to..
send findCenterPoint quote 20,40,100,200 quote to the current
card
calls from the current card the findCenterPoint handler. But I'm not a big
fan of the quotes and sytax. I typically use:
put 20,40,100,200 into
Bonjour Chipp,
I fully agree :-)
Le 26 sept. 08 à 11:58, Chipp Walters a écrit :
Hi Eric,
This reminds me of another interesting shortcut for use with send
to..
send findCenterPoint quote 20,40,100,200 quote to the
current
card
calls from the current card the findCenterPoint
Scott Rossi wrote:
Recently, Richard Gaskin wrote:
The only one I can think of offhand is value, which executes at about
the same speed as do:
put the long id of field 1 into tField
put the number of lines of value(tField)
I would say the benefit of this is being able to avoid
put the number of lines of value(tField)
Rev refuses to compile this:
delete line 2 of value(tField)
Error reads: Commands: missing ','
Any idea why?
Well, I'm assuming it's thinking that you want to evaluate the expression
tField using some other object (the second optional
Bonsoir Richard,
As I said in a previous post, it seems that you *must* require or set
a property.
In your example you don't get or set a property.
See the quote below.
Le 26 sept. 08 à 11:28, Eric Chatonet a écrit :
Bonjour Scott,
The rule is rather simple when working with long IDs or
Eric Chatonet wrote:
As I said in a previous post, it seems that you *must* require or set
a property.
In your example you don't get or set a property.
Correct: in the first example from my earlier post, that's true.
But in the post you quoted we seem to be on the same page:
It seems the
Bonsoir Richard,
I'm sure we are on the same page :-)
In a previous post, you asked me what I thought about Win ribbons and
I did not reply :-(
Probably should we discuss about this off list but, here are my first
feelings:
Actually, ribbons seem to be a kind of 'visual' contextual menus eg
Eric Chatonet wrote:
In a previous post, you asked me what I thought about Win ribbons and
I did not reply :-(
Probably should we discuss about this off list
I'm hoping the folks here find this relevant, though if anyone expresses
annoyance I'm happy to move it offline.
While we're all
17 matches
Mail list logo
