Hi,
Is there a way the one Pro IV Supelayer function can detect that another Pro IV superlayer function is currently running ?
Click the link below to see the new game I'm developing!
2 replies to this topic
#2
Mike Nicholson
-
- Members
-
- 196 posts
Expert
- Gender:Male
- Location:Stockholm, Sweden
Posted 30 March 2007 - 06:59 AM
Not built in.
Add to a lock file at the beginning of a function and remove it at the end. Check that in the other function. That's the most common way of doing it. I'd suggest you add in info such as date/time, operator & terminal ID - it'll make it easier to find out who's stopping you running other things later on
Cheers
Mike
Add to a lock file at the beginning of a function and remove it at the end. Check that in the other function. That's the most common way of doing it. I'd suggest you add in info such as date/time, operator & terminal ID - it'll make it easier to find out who's stopping you running other things later on
Cheers
Mike
#3
Lewis Mccabe
-
- Members
-
- 455 posts
ProIV Guru
- Gender:Male
- Location:Sarasota, Florida
Posted 30 March 2007 - 02:11 PM
Nick,
On version 5.5 you can call functions from global logics. We have global logics HOUSEIN and HOUSEOUT (house for "housekeeping") which we place in logic in and out of each function respectively. We do multiple global function calls in each one without much of a performance hit. We did employ memory files where necessary. On global functions which are called often during updates we cannot employ for performance reasons but this turns out to be seldom. Initially, we created the housekeeping logics for capture of function execution information but found additional uses as well - security, setting of user environment, event logs, etc. If you have access to bootstrap files you can simply add to logic in and out through an update.
If this is the route you think you would like to go, I can give you additional information.
Lew
On version 5.5 you can call functions from global logics. We have global logics HOUSEIN and HOUSEOUT (house for "housekeeping") which we place in logic in and out of each function respectively. We do multiple global function calls in each one without much of a performance hit. We did employ memory files where necessary. On global functions which are called often during updates we cannot employ for performance reasons but this turns out to be seldom. Initially, we created the housekeeping logics for capture of function execution information but found additional uses as well - security, setting of user environment, event logs, etc. If you have access to bootstrap files you can simply add to logic in and out through an update.
If this is the route you think you would like to go, I can give you additional information.
Lew
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
