Re: Newbie Question - Hidden Password
Re: Newbie Question - Hidden Password
- Subject: Re: Newbie Question - Hidden Password
- From: Paul Berkowitz <email@hidden>
- Date: Fri, 08 Jun 2001 20:52:38 -0700
On 6/8/01 5:14 PM, "J. B. Stewart" <email@hidden> wrote:
>
> Is there a way in which I can hide the values being entered into the password
>
> dialog that are hidden - like *******
>
--
>
Yes
>
>
There are 2 that I know of, first is Dialog Director which no scripter should
>
be without
I've been looking into DD recently and wonder if those with more experience
can answer a few questions.
1) Using live dialogs with 'dd install', I find that in OS 9.1/AS1.6, 'dd
delete dialog' does not work well OMM. Instead of deleting the front dialog
and letting the next one behind carry on normally, everything freezes with
mostly-blank and unavailable dialogs and apps. Running 'dd uninstall' in a
script editor is the only way to get out of the mess.
The workaround I've used is to continually update the records which created
the dialogs every time something is changed by 'dd set' or 'dd make'. Then I
can get the various current bounds of dialogs beneath the top one, via 'dd
get bounds', do a 'dd uninstall', a 'dd install' and recreate the lower
dialogs according to the up-to-date records. It works, and recreates fast,
albeit with a brief blip, but is there a better way? Does everyone have the
freeze problem in OS 9.1 with 'dd delete dialog'?
2) I've found that keeping dialog records current is also necessary because
there are so may instance where 'dd set' will not work (bounds -aside from
push buttons and whole dialogs - , class, etc. It works fine for value and
usually for contents of dialog items), and 'dd get' is mostly ineffectual.
So 'dd delete' of a dialog item is necessary, then 'dd make' for its
replacement if it's a different class of item or you want to move it -
except that you _can_ set bounds of push buttons. Because deleting a dialog
item removes it from the dialog's 'item' list and the dialog record's
contents list, and pushes the index of all subsequent items up one, revising
the dialog record is tricky. What's much worse is if a set of dialog items
belong together (perhaps their item indices are recorded in a separate
script record), then that record is thrown out of kilter by a 'dd delete'
and a 'dd make' which makes the new item at the end of the contents list.
I've found an extremely intricate way to continually update my script
records or lists, but wonder if anyone has found an easier workaround.
3) I'm about to try 'gauge' for a progress bar, but worry again about
deleting it at the end. Does it run simultaneously with app events that it's
meant to track? It looks as if it will only work with repeat loops, not
whose clauses for apps that implement the, which is a shame, as it then
means everything has to go slower than otherwise. Any tips?
Thanks in advance for any suggestions.
--
Paul Berkowitz