09-02-2011, 09:45 AM
1. I don't think you can currently know the type of user, but that could be added to the return info upon successful login easily enough I think.
2. Typically you don't worry so much about the state of the device, but just fields. If the device is not connected, the fields will be in error state. Since everything is basically driven by fields, this is usually fine. And of course some fields can be in error state even if their associated device is connected.
3. There's no way for you to know, and the same applies at my level as well. At the action editor level they are passed in a quoted comma list, so it's open ended. They would just have to have documentation on the macro being invoked so that they know what to pass.
2. Typically you don't worry so much about the state of the device, but just fields. If the device is not connected, the fields will be in error state. Since everything is basically driven by fields, this is usually fine. And of course some fields can be in error state even if their associated device is connected.
3. There's no way for you to know, and the same applies at my level as well. At the action editor level they are passed in a quoted comma list, so it's open ended. They would just have to have documentation on the macro being invoked so that they know what to pass.
Dean Roddey
Explorans limites defectum
Explorans limites defectum