Newbie question about image/button relationships

[Judy Perry]

Or, Jason,

In perhaps a more 'brain-friendly' fashion, simply create a number of
buttons whose type is "transparent" -- these will respond just fine to
mouse events.

How to do it?  Create a button by dragging the button tool over from the
tools palette to the area on your phone image; resize to fit desired area;
double-click to bring up its properties palette.  The current 'style' is
probably set to "push-button" but using that drop-down or options type
button, you can it to "transparent".  Be certain to uncheck the "show
name" property.  Give it a name you're likely to recall (but IIRC, don't
use numbers or other reserved words).

HTH,

Judy
patron saint-in-training for newbie non-programmers.


On Mon, 22 Nov 2004, Klaus Major wrote:

> Hi Jason,
>
> > Hello all,
> >
> > This is my first post to the use-revolution mailing list, and I have a
> > question about what images/buttons can (or cannot) do.  Our company has
> > chosen Revolution to create prototypes of handset applications, so we
> > can mock them up and find potential areas of confusion before
> > committing
> > to the user interface of the application.  I only have a handful of
> > programming knowledge, as my background is in Human-Computer
> > Interaction, focusing on UI design and usability; this is also my first
> > experience with a "card-based" language.
> >
> > Now, onto the issue.  I have an image of a mobile phone keypad (in JPG
> > format), and I would like for the user to be able to click on specific
> > areas, causing changes to occur on the "screen" (which is a field).  Is
> > there a way to Revolution to watch for specific areas of the image to
> > be
> > pressed (such as the coordinates of a "Send" key, vs. the coordinates
> > of
> > an "End" key)?  Keep in mind, this is only one image, not a bunch of
> > images.  If this is not possible, do I have to create a group of
> > buttons
> > on top of the image that are all set so they are not visible?
>
> Almost :-)
>
> A bunch of buttons is OK, but when they are invisible (hidden) they are
> also invisible to the mouse...
>
> You can set their "ink" to "noop", then they will respond to
> mouseclicks etc...
> but are invisible to our eyes :-)
>
> Hope that helps.
>
> > Thank you in advance for your help.  I'm happy that a mailing list like
> > this exists!
> >
> > Best regards,
> > Jason Silver
> >
> > Human Factors Engineer, Sr.
> > QUALCOMM Inc.
> > jsilver at qualcomm.com
>
> Regards
>
> Klaus Major
> klaus at major-k.de
> http://www.major-k.de
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>