> On 6/6/00 6:48 pm, LORI FRAIND <[EMAIL PROTECTED]> wrote:
>
> > A few basic questions about the MetaCard interface itself:
> >
> > The only place I can find the Icons button is on the Stack Properties
> tab.
> > Unfortunately, when I select an icon for the button I'm creating, the
> Icon
> > Chooser auto-closes, so I have to go back to the Stack properties and
> call
> > up the Icon Chooser for each button I want to assign an icon to.
>
You need the ID of the image - try opening up the icon chooser and checking
the ID of the image you want (e.g. moving the mouse over the icon and typing
"put the ID of the mouseControl" in the message box).
Thank you for your responses. I guess my real question about the Icon
Chooser is whether there is another way of accessing it than through the
Stack Properties (when where I mostly will want to use it is for buttons),
and whether there is a way to keep it up, as it is possible to let the font
and color boxes up indefinitely.
> > More advanced question: I prefer to work with my Windows 98 screen set
> to
> > 1600x1200 pixels (just so everybody at the office will make fun of me
> for
> > the wee text nobody else can read), but won't be developing for this
> > resolution. We actually want to develop for full screen display on
> HP-UNIX
> > and Windows NT systems (for which I know no other specifications). I
> will,
> > however, be developing the storyboards (right now trying to do it in
> > MetaCard, learn as I go!) on the Windows 98. If everything works out
> well,
> > we will develop the running files directly from the WYSIWYG storyboards.
> So
> > what is the question? How can we script the stack to transfer without
> too
> > much pain from my 1600x1200 screen to automatically fill the screens of
> > other systems, regardless of resolution?
>
> Design your stack at a common resolution that everyone will have: 800x600
> is
> fairly typical. If the user has a larger screen than that which you want
> to
> cover, set the backDrop property.
>
As we have a lot of stuff to put on each screen, we need to use as
much real estate as we can. Also, I know that one of the aspects that played
against MetaCard during our grueling trade study was that our HTML
programmers had figured out how to make a browser screen dynamically set
itself to fill the whole screen. So I don't think the backdrop will be a
viable solution, since I know there are some folks here who are just waiting
to tell me they told me so, and we should have gone with
HTML/JavaScript/Perl/etc. adnauseum.
> Regards,
>
> Kevin
>
> > Thank you!
> >
> > Lori C. Fraind
> > Delex Systems, Inc.
> > (703) 734-8300 x310
>
> Kevin Miller <[EMAIL PROTECTED]> <http://www.xworlds.com/>
> Cross Worlds Computing, MetaCard Distributors, Custom Development.
> Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707.
>
>
> Archives: http://www.mail-archive.com/metacard%40lists.best.com/
> Info: http://www.xworlds.com/metacard/mailinglist.htm
> Please send bug reports to <[EMAIL PROTECTED]>, not this list.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
