I have tried using the TIMER event over and

over again but each time it does not work!

It indeed looks to me like there is a bug in it.

I would be most grateful if any one can prove me wrong.

Yaw:

there are two steps to using the timer event.

You need to place code on the event and you need to turn it on

make a simple form called 'TIMER', no table.

put a single editline control on it, name it "clock"

In the Create event of your form, put

@@window-]timer= 5000:@fm:0

This should make the event fire every 5 seconds

In the timer event try

.Clock-]Text=timedate()

run your form.

It should update the clock field every 5 seconds

Hope this helps

Bob

Bob/other RTI'ers,

Would it be asking too much when you post a response that you don't use the shorthand for Set and Get Property.

For various reasons, we don't use the Event script very much so there's was no incentive for us to learn the shorthand form. We call nearly everything in the Quick Events via commuter modules. This keep the Events script for each form very light.

Don't know how others feel about this, but there may be others who feel the same way. "Pull out the book and try to interpret what this shorthand is saying." What a pain .

My 2cents and operating on limited bandwidth. Thanks again for all your help.

Ray

Ray,

I for one agree with you.

- Oystein -

Ray-

We use the shorthand because we're bad typists.

the syntax is:

value=.control_name-]property

    or

value=@variable_name-]property

so, to get the text property of the TITLE control,

value=.title-]text

but, if we want to get the text property of CtrlEntID, then

value=@ctrlEntID-]text

if the variable already has an @ in front, add another anyway

value=@@window-]text

Set_properties use the same rules, just put the equals on the other side of the equation.

to set the Title control's text property, you'd go

title-]text=New Text'

or

@CtrlEntID-]enabled='

or

@@Window-]visible=3

Clear?

Mike

Growl…geerrr…growl…geeerrr.. Very funny, but frustrating.

Short-hand is okay for heavy duty techno-guys, but I like to make our system less mysterious, more open to everyone for easier maintainance, and easier to understand. The clarity and self-documenting syntax of Set_Property and Get_Property is a plus and we would use them even if we were to incorporate the use of Event Scripts more. Why have two languages for the same thing?

It's enough just teaching people Set and Get without shorthand. Everyone can quickly understand Set and Get. Shorthand, well it's just that, short, but harder to understand.

Hey again, thanks for OI32 and may you be bless with many lanpacks.

Ray

My main objection with the shorthand notation is you often have to convert it to longhand. E.g you have programming starting out as scripted events that you later convert to SPs called by quickevents. E.g you have programming you get from others you want to include in your SPs.

Can't admit I don't understand it of course.

- Oystein -

Oystein,

Ditto your comment.

However, due to my low-level of pride, I have no hesitation in admitting my ignorance or intolerance for anything that might make things harder

Have a nice day!

Ray

BOB, You've made my day! Thanks a lot!!

I wish also to thank everyone else who made the

effort to give me a solution, especially Revelation

Support.

Yaw

View this thread on the forum...