I have always followed the 'You create it then you manage it' code rule. This rule is also true for other functions like SetRedraw() and until recently I would have said SetPointer().
I have come across an issue where I need to set the pointer before doing some work. My problem is my application has a ton of services (like the PFC) that can be called from multiple places and called multiple times as well as calling itself. There is no single entry/exit point. If I add SetPointer(Hourglass!) and SetPointer(Arrow!) to all my functions then I will get some nice flashing which I don't want. Now, reading the help on SetPointer() it says the Pointer will get reset after the script ends which then made me wonder...what if I just set the pointer in all the functions and not set it back? As I began implementing I felt the Codeing Police would be knocking on my door soon but to my amazement I ended up with the result I was needing to fix my issue. The Pointer didn't flash and it returned back to Arrow after all the functions were executed.
So, my question to you all is do I not need to worry about setting the Pointer back? It just doesn't seem right to me but if this is the proper way to handle the Pointer and others are doing that as well then I am good with it - especially since it solves my problem.
Thanks for your input!
Chris Craft