🚀 go-pugleaf

In article <17588.9405240918@potter.cc.keele.ac.uk>, "D.W. Emley" <gga12@CC.KEELE.AC.UK> writes:
> The best way I've found to make input text invisible is to make the text
> colour the same as the background. To do this, set up your text input
> interaction as normal. Run the program and select PAUSE when text input is
> required. Double-click on the text input rectangle to select it. Now you can
> change the background and foreground colour of the text as normal.
> 
> This is also the way in which you can change the font and size of user input
> text as I learned to my cost. In APW Aware chooses the "system" font by
> default for all input text or text labels on buttons. This is great until
> you try to run your program on a PC that doesn't have this font installed.
> You can then get some funny effects when Windows tries to map the nearest
> equivalent font. Normally this manifests it self in form of text labels
> being larger than the buttons. You can alter the font for input text as I've
> shown and I've found it best to use the fonts shipped with Windows eg. MS

A word of caution here-It is also possible the Windows fonts still have the 
same problem of "enlarging".  You might want to look to the video driver on 
th eplayback system as the culprit.  Some drivers which have th option for 
large and small fonts can also be a problem.  The best solution so far is to 
spec a recommended configuration which suggests the standard windows driver 
and not the third party.  Furthermore some of the 
enlarging of text tends to go away if you go back, highlight the text in 
question and re-apply the font, and font size, even though you may have 
confirmed these attributes.

There is also a product called INSTALLIT which allows you to load fonts 
during install (see my previous reply).  This could eliminate some of the creative constraints 
encounterd by using the windows supplied fonts.

Good luck!



> Sans Serif to avoid this problem. However, it does not appear possible to
> change the font used to label buttons. I've therefore used my own buttons

According to Macromedia Tech support this funtion (changing button fonts) was 
not developed in time for the current release of APW.  Maybe we should look 
for it in future releases.

> and labels and used a "touch area" interaction instead of the usual "button
> interaction".
> 
> Dave Emley : gga12@cc.keele.ac.uk


David Conner
93conner@piglet.wmich.edu