director and FLASH mouse clicks with touchscreens

[lynne sheldon]

hi,
If anyone else knows about the bug in director and a possible solution
please let me know!

Basically, if you have a flash movie, with on(release) actions on buttons,
then import into director
as a sprite, then, using a touchscreen, the on(release) does NOT work
properly. You have to double
click every button to get it to work.

Any idea anyone?

[Jon Grubb webforumsuser@macromedia.com]

You can overcome this by defining the behaviours of the buttons in Director

i.e.

on mouseDown
do this
end

and so on...

Jon Grubb

[url]http://www.jongrubb.com/[/url]

[Rob Dillon]

Normally, when working with touch screens you a much more resticted set
of interface controls. It's been my experience that most touch screens
react to the mouse down event more reliably than the mouse up event and
most don't have any idea what to do with a drag event, either mouse up
or mouse down.

The touch screen should have some instructions for what events it will
work with.

--
Rob
_______
Rob Dillon
Team Macromedia
[url]http://www.ddg-designs.com[/url]
412-243-9119

[url]http://www.macromedia.com/software/trial/[/url]

[lynne sheldon]

The touch screen works perfectly with ANY application that isn't a DIRECTOR
application.
i.e. that is to say, if the flash sprite, was a FLASH projector, then the
buttons would work perfectly.

It only doesn't work properly, if its embedded and published as a director
exe. The actions are
attached to the button in the FLASH sprite and not in director.



"Rob Dillon" <rob@ddg-designs.com> wrote in message
news:230120040910490379%rob@ddg-designs.com...

> Normally, when working with touch screens you a much more resticted set
> of interface controls. It's been my experience that most touch screens
> react to the mouse down event more reliably than the mouse up event and
> most don't have any idea what to do with a drag event, either mouse up
> or mouse down.
>
> The touch screen should have some instructions for what events it will
> work with.
>
> --
> Rob
> _______
> Rob Dillon
> Team Macromedia
> [url]http://www.ddg-designs.com[/url]
> 412-243-9119
>
> [url]http://www.macromedia.com/software/trial/[/url]

[lynne sheldon]

how though? My application is a flash sprite, with action script attached to
every button.

i.e

on (release) {

gotoAndPlay("some element");
}

How would this translate through to director lingo? The file is huge, and
there's hundreds of buttons all with
their own actionscript attached to them. And just as relevant, is why, isn't
it working!!???

onMouseDown do what exaclty?? I would have to define a seperate action for
everyone of my flash
buttons if i did it the lingo route. What a nightmare!







"Jon Grubb" <webforumsuser@macromedia.com> wrote in message
news:bur60q$rls$1@forums.macromedia.com...

> You can overcome this by defining the behaviours of the buttons in

Director

>
> i.e.
>
> on mouseDown
> do this
> end
>
> and so on...
>
> Jon Grubb
>
> [url]http://www.jongrubb.com/[/url]

[Michael Hamstra]

The touchscreen is simply another input device, it uses "mouse emulation"
software. The software doesn't know whether it is a mouse, touchscreen, pen
stylus...

I agree with Rob, I prefer to use the mouseDown when working with
touchscreens, seems more reliable. Also, no need for the mouseEnter and
mouseLeave as users are typically just "touching" a button. Note to also
make your buttons large enough to handle calibration drift of the
touchscreen as well as various size fingers...

Michael Hamstra



"lynne sheldon" <sales@ukretailer.freeserve.co.uk> wrote in message
news:buracv$4ia$1@forums.macromedia.com...

> The touch screen works perfectly with ANY application that isn't a

DIRECTOR

> application.
> i.e. that is to say, if the flash sprite, was a FLASH projector, then the
> buttons would work perfectly.
>
> It only doesn't work properly, if its embedded and published as a director
> exe. The actions are
> attached to the button in the FLASH sprite and not in director.
>
>
>
> "Rob Dillon" <rob@ddg-designs.com> wrote in message
> news:230120040910490379%rob@ddg-designs.com...

> > Normally, when working with touch screens you a much more resticted set
> > of interface controls. It's been my experience that most touch screens
> > react to the mouse down event more reliably than the mouse up event and
> > most don't have any idea what to do with a drag event, either mouse up
> > or mouse down.
> >
> > The touch screen should have some instructions for what events it will
> > work with.
> >
> > --
> > Rob
> > _______
> > Rob Dillon
> > Team Macromedia
> > [url]http://www.ddg-designs.com[/url]
> > 412-243-9119
> >
> > [url]http://www.macromedia.com/software/trial/[/url]

>
>

[Rob Dillon]

It may be some sort of focus problem. Are your Flash sprites set to be
direct to stage? Are there any functions attached to the Flash sprites
that could interfere?

--
Rob
_______
Rob Dillon
Team Macromedia
[url]http://www.ddg-designs.com[/url]
412-243-9119

[url]http://www.macromedia.com/software/trial/[/url]

[lynne sheldon]

I've tried direct to stage it doesn't make a difference. Ive got many years
experience of touch screens, as I supply my software onto 8,000 touch screen
kiosks. It's definately a quirk of director. No other software has any
problems and indeed FLASH itself, as either an SWF or as .exe projector
works perfectly. It's only if you
import the flash into director that you get the problem.

The flash once imported, only senses the on rollover and on rollout,
although, it WILL detect on press and on release if you double tap the
screen. Its weird. I've tried getting round it by using the on rollover,
then getting director to move the cursor outside the bounds of the sprite,
but this is a fudge.

Its nothing to do with the settings of the touch screen, calibration or
anything else. I've got three different touch screens here, and all have the
same effect.

I am stuck.


"Rob Dillon" <rob@ddg-designs.com> wrote in message
news:230120041208269243%rob@ddg-designs.com...

> It may be some sort of focus problem. Are your Flash sprites set to be
> direct to stage? Are there any functions attached to the Flash sprites
> that could interfere?
>
> --
> Rob
> _______
> Rob Dillon
> Team Macromedia
> [url]http://www.ddg-designs.com[/url]
> 412-243-9119
>
> [url]http://www.macromedia.com/software/trial/[/url]

[lynne sheldon]

i know, so explain to me then, why the flash as either an swf or .exe
projector works correctly, but as soon as
you take the flash into director, it stops working.

You can create the simplist piece of flash you like, with just a single
button on it, and try it on ANY touch screen, and the problem rears its ugly
head.

"Michael Hamstra" <hamstra@bellsouth.net> wrote in message
news:burj73$h4s$1@forums.macromedia.com...

> The touchscreen is simply another input device, it uses "mouse emulation"
> software. The software doesn't know whether it is a mouse, touchscreen,

pen

> stylus...
>
> I agree with Rob, I prefer to use the mouseDown when working with
> touchscreens, seems more reliable. Also, no need for the mouseEnter and
> mouseLeave as users are typically just "touching" a button. Note to also
> make your buttons large enough to handle calibration drift of the
> touchscreen as well as various size fingers...
>
> Michael Hamstra
>
>
>
> "lynne sheldon" <sales@ukretailer.freeserve.co.uk> wrote in message
> news:buracv$4ia$1@forums.macromedia.com...

> > The touch screen works perfectly with ANY application that isn't a

> DIRECTOR

> > application.
> > i.e. that is to say, if the flash sprite, was a FLASH projector, then

the

> > buttons would work perfectly.
> >
> > It only doesn't work properly, if its embedded and published as a

director

> > exe. The actions are
> > attached to the button in the FLASH sprite and not in director.
> >
> >
> >
> > "Rob Dillon" <rob@ddg-designs.com> wrote in message
> > news:230120040910490379%rob@ddg-designs.com...

> > > Normally, when working with touch screens you a much more resticted

set

> > > of interface controls. It's been my experience that most touch screens
> > > react to the mouse down event more reliably than the mouse up event

and

> > > most don't have any idea what to do with a drag event, either mouse up
> > > or mouse down.
> > >
> > > The touch screen should have some instructions for what events it will
> > > work with.
> > >
> > > --
> > > Rob
> > > _______
> > > Rob Dillon
> > > Team Macromedia
> > > [url]http://www.ddg-designs.com[/url]
> > > 412-243-9119
> > >
> > > [url]http://www.macromedia.com/software/trial/[/url]

> >
> >

>
>

[gimbli webforumsuser@macromedia.com]

i too am having the same problem. initially i had to click 3 times before the buttons work.
however i changed the settings of the touch screen and i still have to click twice before the buttons
work. only buttons that are made flash have this problem. since i was on a tight schedule, i
replaced all the buttons. if anyone has found a solution please reply. thanks.

[Jon Grubb webforumsuser@macromedia.com]

Using Flash in Director movies for touchscreen systems is not advisable. I believe that the problem is with the touchscreen drivers.


Jon Grubb

[url]http://www.jongrubb.com/[/url]