Steve,
I have some thoughts on how I want to do my rain delay - skip.
If there are better ways, please let me know, otherwise I am requesting a bit of information to be presented to the user, so I can accomplish this.
Essentially what I am trying to do is trigger script when anything is done to the event for the zone trigger. The idea is, whenever the event is created/edited/etc., I would add in a call to a script to the created event, which would:
I think the easiest way to do this is to add into all the various sections of the extensions script. To get the name of the event (so I can reference the event reference number for event object manipulation), I think I can make a slew of calls to access to get this information out of the mdb. Learning to access ... access along the way! So, I would then be able to get the event reference and I would need to add in a call to the weather checker script.
The advantage to this is, you get to see what the weather has been up to this point and it all ties to the time of the event. I used to do this by just creating an event by hand, which performed the check and skip. However, today I noticed things were still watering on me. Firstly, I goofed up. I did not remember to edit my checker script when I changed the time of the Zone run. So, the Zone was running BEFORE the skip call. Then it would not run the next day because it was skipped.
I realize I could just make a call in the extensions to edit MY self created events to just move them around, but I think it would be good to be able to tie these two together as one event. If it is too much effort, I totally understand!
Again, I am not tied to this and could certainly just create events by hand and make them trigger "1 minute before the time" set for the zone, but instead of my trying to replicate the access commands, I thought I'd ask to see if you could provide a bit more access in the snevl scripts.
I would want event name, maybe trigger time or some other information. I guess the big one is the event name. From there, I get the event reference and can get all the information I need to generate a new event triggering 1 minute BEFORE the snevl event - so I can call a skip to that zone if needed.
If not, maybe have an ability to add on a call to an event "before" the trigger of a zone? I'm not sure how I would go about this, but I think having something trigger prior to the zone going off gives me the ability to AT THAT TIME check the weather to see if I need to skip.
Same with my rain monitor. I have a "clicky" cup type device, which I am going to tie into a DS10A. I am going to get it "calibrated" by watching the amount of rain the receiver states I get, and I compare that to the amount of cup tips so that I can also use this as in input to the script. I think Pete_C was also going to try to calibrate one of these. I wonder if he ever did... Would save me from having to figure it out!
Thanks, sorry about the rambling!
--Dan
I have some thoughts on how I want to do my rain delay - skip.
If there are better ways, please let me know, otherwise I am requesting a bit of information to be presented to the user, so I can accomplish this.
Essentially what I am trying to do is trigger script when anything is done to the event for the zone trigger. The idea is, whenever the event is created/edited/etc., I would add in a call to a script to the created event, which would:
- update the weather information
- look at the current weather
- determine if the event should run
- skip if necessary, otherwise don't do anything (since the next time the event is created the call to the script will be added into the event.
I think the easiest way to do this is to add into all the various sections of the extensions script. To get the name of the event (so I can reference the event reference number for event object manipulation), I think I can make a slew of calls to access to get this information out of the mdb. Learning to access ... access along the way! So, I would then be able to get the event reference and I would need to add in a call to the weather checker script.
The advantage to this is, you get to see what the weather has been up to this point and it all ties to the time of the event. I used to do this by just creating an event by hand, which performed the check and skip. However, today I noticed things were still watering on me. Firstly, I goofed up. I did not remember to edit my checker script when I changed the time of the Zone run. So, the Zone was running BEFORE the skip call. Then it would not run the next day because it was skipped.
I realize I could just make a call in the extensions to edit MY self created events to just move them around, but I think it would be good to be able to tie these two together as one event. If it is too much effort, I totally understand!
Again, I am not tied to this and could certainly just create events by hand and make them trigger "1 minute before the time" set for the zone, but instead of my trying to replicate the access commands, I thought I'd ask to see if you could provide a bit more access in the snevl scripts.
I would want event name, maybe trigger time or some other information. I guess the big one is the event name. From there, I get the event reference and can get all the information I need to generate a new event triggering 1 minute BEFORE the snevl event - so I can call a skip to that zone if needed.
If not, maybe have an ability to add on a call to an event "before" the trigger of a zone? I'm not sure how I would go about this, but I think having something trigger prior to the zone going off gives me the ability to AT THAT TIME check the weather to see if I need to skip.
Same with my rain monitor. I have a "clicky" cup type device, which I am going to tie into a DS10A. I am going to get it "calibrated" by watching the amount of rain the receiver states I get, and I compare that to the amount of cup tips so that I can also use this as in input to the script. I think Pete_C was also going to try to calibrate one of these. I wonder if he ever did... Would save me from having to figure it out!
Thanks, sorry about the rambling!
--Dan
Comment