Page 1 of 1

Do OperatorID settable and onexit() function

Posted: April 23rd, 2018, 10:51 pm
by htuser
Dear Cspro Developer Team,
I find that it's important to have an OperatorID settable programmatically in the future.
Why?
In a menu, sometimes developers may want to ask or no this. Now, it can be asked or no in the pff.
However, it's more simple to have a way to do that programmatically. Actually, the only way to do this for
a menu is to write another program (menu) for writing a pff for the principal menu.
This can be more simple...

Also, i think it's important to have OnExit function inside logic.
Why?
Now, it's available for pff. It will be more dynamic if we can have it inside logic. By example, since we can't sync a running application inside itself logic, having this will allow us to run another application able to sync automatically exiting main application. Since, i use self destructing pff for the main application for severals reasons (by example for avoiding enumerators to modify pff parameters etc.), having OnExit function inside logic is only a solution.

Thanks in advance,

Re: Do OperatorID settable and onexit() function

Posted: April 24th, 2018, 10:08 am
by Gregory Martin
If I understand you correctly, both are currently possible:

1) There is a setoperatorid function: http://www.csprousers.org/help/CSPro/se ... ction.html

2) If you call execpff on Android without the stop parameter, then the PFF is queued for execution after your program closes. You can use this to determine, in logic, if you want to open another PFF after your program executes.

Re: Do OperatorID settable and onexit() function

Posted: April 24th, 2018, 9:19 pm
by htuser
Hi Greg,
Thanks a lot for your prompt response.
However for 1) There is a setoperatorid function:It's an option to show or not the "Enter your Operator ID dialog box, not to set a predefined operator ID. So, the setOperatorid isn't appropriate.
2) PFF is queued:You're correct. It's a good solution.

Best,