pete at mollysrevenge.com
Tue Dec 14 03:29:03 EST 2010
I didn't update the code snippet. I put the dialogdata into a local
variable right after coming back from the modal prompt. I want this
process to be automated so that's why I don;t use the message box -
I'd forget to do it! I could use an "ask" dialog, it's just that my
prompt dialogs are kinda customised for my application.
In answer to your other reply, what you're doing is exactly what I'm
doing to display the version in an About dialog, along with the build
date as well which is also stored in a main stack custom property
(which works fine!).
-------------- next part --------------
On Dec 13, 2010, at 6:29 PM, J. Landman Gay wrote:
> On 12/13/10 7:51 PM, Peter Haworth wrote:
>> Hi Jacquie,
>> I'm certain the prompt handler is returning the correct value - I
>> put an
>> answer information in it right before the set statement and it showed
>> that the dialogdata had the value I keyed into the prompt form.
> Ask and answer dialogs change the value of the dialogdata, but I
> understand it was just a test.
> I can't think of any other reason it would fail. Dialogdata is just
> like a huge engine-wide global and you can use it however you want.
> But any other dialog or modal can change its value so it isn't
> dependable except immediately after it's set. The sample script you
> posted should work, you were doing it right.
> I'm not sure what the goal is of opening a modal to request a
> version number. Is there a reason not to use the message box or an
> "ask" command?
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode