...thanks Robert but 'do login()' was working just fine until I moved it from a
login 'card' in the mainstack into into a login substack.
And it does again now, since I have taken Jaque's advice to use groups with
switched visibility (and background images that simulate popping a substack
with
On 04.06.2011 at 12:58 Uhr +0100 Keith Clarke apparently wrote:
Hi Jim,
Thanks for the response, clarification and tips.
This app has one MainStack (so far!) and it's script contains a
handler on preOpenStack, to start using stack "SOAP". So, thanks for
confirming that this should place the SO
Hi Jim,
Thanks for the response, clarification and tips.
This app has one MainStack (so far!) and it's script contains a handler on
preOpenStack, to start using stack "SOAP". So, thanks for confirming that this
should place the SOAP substack into the message path library 'slot' for the
MainSta
On 4 Jun 2011, at 09:07, Keith Clarke wrote:
Hi folks,
I'm using a substack 'Credentials' as a dialogue box to capture
login credentials for a web service (tUsername, tPassword).
A second 'SOAP' substack acts as a library managing the various
POST messages for the web service, including a
Hi folks,
Problem solved - I dropped the Login substack in favour of the simpler solution
of a card in the MainStack.
Now the SOAP substack is in its message path - and I can put off learning send
and dispatch for another day!
Best,
Keith..
On 4 Jun 2011, at 09:07, Keith Clarke wrote:
> Hi fol
Hi folks,
I'm using a substack 'Credentials' as a dialogue box to capture login
credentials for a web service (tUsername, tPassword).
A second 'SOAP' substack acts as a library managing the various POST messages
for the web service, including a function login pUsername pPassword
If I attempt t
