|
Home > Archive > Macromedia Flash Server > March 2006 > Flash Paper bug fix
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Flash Paper bug fix
|
|
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 7:48 am |
| Not strictly FMS/FCS related, but has anyone here looked closely at the
Flash Paper "fix" provided here:
http://www.flashcomguru.com/index.c...r-Flashpaper2-b
ug
An excerpt:
mc.gMainView.m_mainMC.onMouseDown = function() {
var fpfocus:MovieClip = _global.FPUI.Component.focusedComponent;
if (fpfocus != null) {
// blah
// blah
}
}
What does this actually do, besides simply killing the onMouseDown? As far
as I can tell, _global.FPUI.Component.focusedComponent always returns
undefined.
Thanks,
-Jorge
_____________________
Jorge Maiquez
Digital Samba, S.L.
c/ Llacuna 162
08018 Barcelona, Spain
Tel.: +34 93 401 98 77
Fax.: +34 93 300 90 15
Mob.: +34 647 236 027
http://www.digitalsamba.com <http://www.digitalsamba.com/>
This e-mail is intended for the named addressee only. It may contain
confidential and/or privileged information. If you have received this
message in error, please let us know and then delete this message from your
system. You should not copy the message, use it for any purpose or disclose
its contents to anyone.
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
| I think the comments from the Macromedia guys explain the problem quite
well:
////////////////////
This is a truly heinous fix for an awful problem.
The problem: FP2 content has an onMouseDown handler
that says, "if you clicked somewhere other than
what I think the currently-focused component is,
call Selection.setFocus(null)". This is bad because
calling Selection.setFocus(null) tends to completely
confuse the v2 FocusManager,with the net result being
that we end up "dropping" a mousedown event when FP2
content is embedded inside something that uses v2 components.
This "workaround" (actually, "hack") actually dives in
to the content (which we ASSUME TO BE FLASHPAPER)) and
actually replaces the offending onMouseDown handler with a
less-harmful one.
Yes, this is incredibly evil, but an expedient solution
given the nature and timing of the problem.
So that the problem may be fixed in a future version of
FlashPaper, we check for the (currently nonexistent)
member property of "hasSafeSelectionManagement" in the
FlashPaper.MainView class, and only apply this patch if
said member doesn't exist. If we improve FP2's focus
management in the future, we will define this member so
that this patch does not get applied.
////////////////////////
Basically FP messes up the Focusmanagement in a v2 componentized app.
Another user suggested that if you do not need the Focusmanager then an
easier fix is
focusManager.enabled = false;
This I haven't tried.
I have also experienced another nasty bug which crashes the IDE really hard
when you try and load FP from a full http:// URL. Someone on this list
suggested that security.allowdomain will fix this - I haven't tried that
either.
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 08:45
> To: 'FlashComm Mailing List'
> Subject: [FlashComm] Flash Paper bug fix
>
> Not strictly FMS/FCS related, but has anyone here looked
> closely at the Flash Paper "fix" provided here:
> http://www.flashcomguru.com/index.c.../Workaround-for
> -Flashpaper2-b
> ug
>
> An excerpt:
>
> mc.gMainView.m_mainMC.onMouseDown = function() {
> var fpfocus:MovieClip = _global.FPUI.Component.focusedComponent;
> if (fpfocus != null) {
> // blah
> // blah
> }
> }
>
>
> What does this actually do, besides simply killing the
> onMouseDown? As far as I can tell,
> _global.FPUI.Component.focusedComponent always returns undefined.
>
> Thanks,
> -Jorge
>
>
> _____________________
> Jorge Maiquez
>
> Digital Samba, S.L.
>
> c/ Llacuna 162
> 08018 Barcelona, Spain
> Tel.: +34 93 401 98 77
> Fax.: +34 93 300 90 15
> Mob.: +34 647 236 027
> http://www.digitalsamba.com <http://www.digitalsamba.com/>
>
>
> This e-mail is intended for the named addressee only. It may
> contain confidential and/or privileged information. If you
> have received this message in error, please let us know and
> then delete this message from your system. You should not
> copy the message, use it for any purpose or disclose its
> contents to anyone.
>
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 7:48 am |
| Sure, nice explanation, but the code doesn't do anything 
> "actually replaces the offending onMouseDown handler with a =
less-harmful
one"
Erhm.. no.. it replaces the offending onMouseDown handler with nothing,
because the code inside the handler NEVER runs because fpfocus is ALWAYS
undefined (I've put traces inside this handler to test this).
Fair enough, this "fix" does take care of issues relating to focus
management with other V2 UI components, but it just seems strange to me =
that
the code doens't ever run.
And for some added fun with Flash=A0Paper, try placing anything =
draggable on
top of FP content and drag it around (as in the example,
http://www.macromedia.com/devnet/fl..._flpaper2.html=
).=20
If you enable scrolling, and then drag the MovieClip around, you'll see =
that
the content also scrolls, which is not desired behaviour. I found this
problem whilst implementing a pointer component to be used in =
conjunction
with the Flash Paper.. completely useless. Seems like it just evaluates
whether the mouse coordinates are above the content without checking if
another object is on top it.
Cheers,
-Jorge
-----Original Message-----
Wrom: KEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMV
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan =
Richter
Sent: 27 March 2006 11:20
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
I think the comments from the Macromedia guys explain the problem quite
well:
////////////////////
This is a truly heinous fix for an awful problem.
The problem: FP2 content has an onMouseDown handler that says, "if you
clicked somewhere other than what I think the currently-focused =
component
is, call Selection.setFocus(null)". This is bad because calling
Selection.setFocus(null) tends to completely confuse the v2
FocusManager,with the net result being that we end up "dropping" a =
mousedown
event when FP2 content is embedded inside something that uses v2 =
components.
This "workaround" (actually, "hack") actually dives in to the content =
(which
we ASSUME TO BE FLASHPAPER)) and actually replaces the offending =
onMouseDown
handler with a less-harmful one.
Yes, this is incredibly evil, but an expedient solution given the nature =
and
timing of the problem.
So that the problem may be fixed in a future version of FlashPaper, we =
check
for the (currently nonexistent) member property of
"hasSafeSelectionManagement" in the FlashPaper.MainView class, and only
apply this patch if said member doesn't exist. If we improve FP2's focus
management in the future, we will define this member so that this patch =
does
not get applied.
////////////////////////
Basically FP messes up the Focusmanagement in a v2 componentized app.=20
Another user suggested that if you do not need the Focusmanager then an
easier fix is focusManager.enabled =3D false;
This I haven't tried.
I have also experienced another nasty bug which crashes the IDE really =
hard
when you try and load FP from a full http:// URL. Someone on this list
suggested that security.allowdomain will fix this - I haven't tried that
either.
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 08:45
> To: 'FlashComm Mailing List'
> Subject: [FlashComm] Flash Paper bug fix
>=20
> Not strictly FMS/FCS related, but has anyone here looked closely at=20
> the Flash Paper "fix" provided here:
> http://www.flashcomguru.com/index.c.../Workaround-for
> -Flashpaper2-b
> ug
> =20
> An excerpt:
> =20
> mc.gMainView.m_mainMC.onMouseDown =3D function() {
> var fpfocus:MovieClip =3D _global.FPUI.Component.focusedComponent;
> if (fpfocus !=3D null) {
> // blah
> // blah
> }
> }
>=20
> =20
> What does this actually do, besides simply killing the onMouseDown? As =
> far as I can tell, _global.FPUI.Component.focusedComponent always=20
> returns undefined.
> =20
> Thanks,
> -Jorge
> =20
> =20
> _____________________
> Jorge Maiquez
> =20
> Digital Samba, S.L.
> =20
> c/ Llacuna 162
> 08018 Barcelona, Spain
> Tel.: +34 93 401 98 77
> Fax.: +34 93 300 90 15
> Mob.: +34 647 236 027
> http://www.digitalsamba.com <http://www.digitalsamba.com/>
> =20
>=20
> This e-mail is intended for the named addressee only. It may contain=20
> confidential and/or privileged information. If you have received this=20
> message in error, please let us know and then delete this message from =
> your system. You should not copy the message, use it for any purpose=20
> or disclose its contents to anyone.
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
| Jorge,
you're probably not calling
fixFlashPaper2SelectionManagement(dest_m
c); // applies bugfix
once the FP has loaded.
If you did then your traces should show.
Stefan
=20
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org=20
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 11:52
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Sure, nice explanation, but the code doesn't do anything
>=20
> one"
>=20
> Erhm.. no.. it replaces the offending onMouseDown handler=20
> with nothing, because the code inside the handler NEVER runs=20
> because fpfocus is ALWAYS undefined (I've put traces inside=20
> this handler to test this).
>=20
> Fair enough, this "fix" does take care of issues relating to=20
> focus management with other V2 UI components, but it just=20
> seems strange to me that the code doens't ever run.
>=20
> And for some added fun with Flash=A0Paper, try placing anything=20
> draggable on top of FP content and drag it around (as in the=20
> example,=20
> http://www.macromedia.com/devnet/fl...icles/import_fl
> paper2.html).=20
>=20
> If you enable scrolling, and then drag the MovieClip around,=20
> you'll see that the content also scrolls, which is not=20
> desired behaviour. I found this problem whilst implementing a=20
> pointer component to be used in conjunction with the Flash=20
> Paper.. completely useless. Seems like it just evaluates=20
> whether the mouse coordinates are above the content without=20
> checking if another object is on top it.
>=20
> Cheers,
> -Jorge
>=20
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Jorge Maiquez 2006-03-27, 7:48 am |
| Yes I am. Try it for yourself.=20
Put a trace inside the onMouseDown, after the line that reads:
if (fpfocus !=3D null) {
Or trace out the value of fpfocus before this line.
You'll see that in the first case, it never traces, and in the second =
case,
it always traces undefined.
-Jorge
=20
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan =
Richter
Sent: 27 March 2006 13:00
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
Jorge,
you're probably not calling
fixFlashPaper2SelectionManagement(dest_m
c); // applies bugfix
once the FP has loaded.
If you did then your traces should show.
Stefan
=20
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 11:52
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Sure, nice explanation, but the code doesn't do anything
>=20
> one"
>=20
> Erhm.. no.. it replaces the offending onMouseDown handler with=20
> nothing, because the code inside the handler NEVER runs because=20
> fpfocus is ALWAYS undefined (I've put traces inside this handler to=20
> test this).
>=20
> Fair enough, this "fix" does take care of issues relating to focus=20
> management with other V2 UI components, but it just seems strange to=20
> me that the code doens't ever run.
>=20
> And for some added fun with Flash=A0Paper, try placing anything=20
> draggable on top of FP content and drag it around (as in the example,=20
> http://www.macromedia.com/devnet/fl...icles/import_fl
> paper2.html).=20
>=20
> If you enable scrolling, and then drag the MovieClip around, you'll=20
> see that the content also scrolls, which is not desired behaviour. I=20
> found this problem whilst implementing a pointer component to be used=20
> in conjunction with the Flash Paper.. completely useless. Seems like=20
> it just evaluates whether the mouse coordinates are above the content=20
> without checking if another object is on top it.
>=20
> Cheers,
> -Jorge
>=20
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
| I can also confirm that applying
System.security.allowDomain("www.yourdomain.com");
does indeed fix the hard crash when loading a Flashpaper from a full URL
(yourdomain.cm specifies the URL where the Flashpaper is being loaded =
from).
Stefan
=20
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org=20
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> Stefan Richter
> Sent: 27 March 2006 12:00
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Jorge,
> you're probably not calling
>=20
> fixFlashPaper2SelectionManagement(dest_m
c); // applies bugfix
>=20
> once the FP has loaded.
>=20
> If you did then your traces should show.
>=20
> Stefan
>=20
> =20
>=20
> strange to=20
> the example,=20
> behaviour. I=20
> to be used=20
> Seems like=20
> the content=20
>=20
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
| I see what you mean, I get the traces you described.
However I don't understand how or why this is a problem? After all it =
fixes
the bug as described... Looking at the code I presume that the trace =
does
not run because=20
var fpfocus:MovieClip =3D _global.FPUI.Component.focusedComponent;
evaluates to undefined.
I don't know when or how it would evaluate to anything else but if it =
does
it appears to handle that case too. So you are right, it does nothing =
else
apart from killing mc.gMainView.m_mainMC.onMouseDown when used in the =
way
that you or I use it. Ok, it doesn't completely kill it, you can still =
trap
it if you like.
On top of that any other V2 components now stop dropping click events =
which
is what this workaround claims to achieve and apparently does.
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org=20
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> Jorge Maiquez
> Sent: 27 March 2006 12:11
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Yes I am. Try it for yourself.=20
>=20
> Put a trace inside the onMouseDown, after the line that reads:
>=20
> if (fpfocus !=3D null) {
>=20
> Or trace out the value of fpfocus before this line.
>=20
>=20
> You'll see that in the first case, it never traces, and in=20
> the second case, it always traces undefined.
>=20
> -Jorge
>=20
> =20
>=20
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> Stefan Richter
> Sent: 27 March 2006 13:00
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Jorge,
> you're probably not calling
>=20
> fixFlashPaper2SelectionManagement(dest_m
c); // applies bugfix
>=20
> once the FP has loaded.
>=20
> If you did then your traces should show.
>=20
> Stefan
>=20
> =20
>=20
> strange to=20
> the example,=20
> behaviour. I=20
> to be used=20
> Seems like=20
> the content=20
>=20
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com=20
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Jorge Maiquez 2006-03-27, 7:48 am |
| I find that the IDE locks up because a crazy amount of error msgs get
displayed in the output panel when you try to load a remote flashpaper =
into
the (locally) published swf in the IDE. These msgs are of the form:
*** Security Sandbox Violation ***
SecurityDomain 'http://remoteFlashPaper.swf' tried to access =
incompatible
context 'file:///C|/localPublishedFile.swf'
This is resolved by placing the published swf on your webserver, within =
the
allowed domain as defined by the System.security.allowDomain. Locally
however, you will always get these msgs.. that is, I haven't found a way =
to
supress them.
Btw, did you manage to get a trace from within the onMouseDown of the =
Flash
Paper fix?
-Jorge
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan =
Richter
Sent: 27 March 2006 13:13
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
I can also confirm that applying
System.security.allowDomain("www.yourdomain.com");
does indeed fix the hard crash when loading a Flashpaper from a full URL
(yourdomain.cm specifies the URL where the Flashpaper is being loaded =
from).
Stefan
=20
[vbcol=seagreen]
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan=20
> Richter
> Sent: 27 March 2006 12:00
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Jorge,
> you're probably not calling
>=20
> fixFlashPaper2SelectionManagement(dest_m
c); // applies bugfix
>=20
> once the FP has loaded.
>=20
> If you did then your traces should show.
>=20
> Stefan
>=20
> =20
>=20
> strange to
> the example,
> behaviour. I
> to be used
> Seems like
> the content
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
| I get these securityerrors in the IDE only when I publish to Player 8. =
For
Player 7 it seems to works fine.=20
=20
If you place the published swf in the same domain as specified in
System.security.allowDomain does this mean that both published swf and
Flashpaper swf reside in the same domain? In that case I don't think =
you'd
even need System.security.allowDomain.=20
I wonder how the app would run if both swfs were under different domains =
and
accessed via Player 8...
See my other email for the reply on the trace issue.
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org=20
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> Jorge Maiquez
> Sent: 27 March 2006 12:46
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> I find that the IDE locks up because a crazy amount of error=20
> msgs get displayed in the output panel when you try to load a=20
> remote flashpaper into the (locally) published swf in the=20
> IDE. These msgs are of the form:
>=20
> *** Security Sandbox Violation ***
> SecurityDomain 'http://remoteFlashPaper.swf' tried to access=20
> incompatible context 'file:///C|/localPublishedFile.swf'
>=20
>=20
> This is resolved by placing the published swf on your=20
> webserver, within the allowed domain as defined by the=20
> System.security.allowDomain. Locally however, you will always=20
> get these msgs.. that is, I haven't found a way to supress them.
>=20
>=20
> Btw, did you manage to get a trace from within the=20
> onMouseDown of the Flash Paper fix?
>=20
> -Jorge
>=20
>=20
>=20
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of=20
> Stefan Richter
> Sent: 27 March 2006 13:13
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> I can also confirm that applying
> System.security.allowDomain("www.yourdomain.com");
> does indeed fix the hard crash when loading a Flashpaper from=20
> a full URL (yourdomain.cm specifies the URL where the=20
> Flashpaper is being loaded from).
>=20
> Stefan
>=20
> =20
>=20
> Of Stefan=20
> handler to=20
> to focus=20
> around, you'll=20
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 7:48 am |
| > Looking at the code I presume that the trace does not run because var=20
> fpfocus:MovieClip =3D _global.FPUI.Component.focusedComponent;
> evaluates to undefined.
Exactly.
> However I don't understand how or why this is a problem?
I believe that the content scrolling problem, which I described a couple =
of
posts back, could be related to the code in the fix never executing. I'm =
not
exactly sure, but the hitTest would seem to indicate something along =
these
lines. Basically, I think there IS something called focusedComponent in =
the
Flash Paper code, but the targeting in the fix is screwed up.
-Jorge
-----Original Message-----
Wrom: ZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYI
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan =
Richter
Sent: 27 March 2006 13:31
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
I see what you mean, I get the traces you described.
However I don't understand how or why this is a problem? After all it =
fixes
the bug as described... Looking at the code I presume that the trace =
does
not run because var fpfocus:MovieClip =3D
_global.FPUI.Component.focusedComponent;
evaluates to undefined.
I don't know when or how it would evaluate to anything else but if it =
does
it appears to handle that case too. So you are right, it does nothing =
else
apart from killing mc.gMainView.m_mainMC.onMouseDown when used in the =
way
that you or I use it. Ok, it doesn't completely kill it, you can still =
trap
it if you like.
On top of that any other V2 components now stop dropping click events =
which
is what this workaround claims to achieve and apparently does.
Stefan
> -----Original Message-----
> Wrom: YZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOT
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Jorge=20
> Maiquez
> Sent: 27 March 2006 12:11
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Yes I am. Try it for yourself.=20
>=20
> Put a trace inside the onMouseDown, after the line that reads:
>=20
> if (fpfocus !=3D null) {
>=20
> Or trace out the value of fpfocus before this line.
>=20
>=20
> You'll see that in the first case, it never traces, and in the second=20
> case, it always traces undefined.
>=20
> -Jorge
>=20
> =20
>=20
> -----Original Message-----
> Wrom: WFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKP
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan=20
> Richter
> Sent: 27 March 2006 13:00
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> Jorge,
> you're probably not calling
>=20
> fixFlashPaper2SelectionManagement(dest_m
c); // applies bugfix
>=20
> once the FP has loaded.
>=20
> If you did then your traces should show.
>=20
> Stefan
>=20
> =20
>=20
> strange to
> the example,
> behaviour. I
> to be used
> Seems like
> the content
>=20
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com=20
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
| I see.
When you try running your loaded FP and don't apply the fix then does the
drag/hitTest problem still occur?
You could be right and fixing one issue will bring up another...
I do have the original email from MM support somewhere, hit me offlist if
you think it would be worthwhile following up with one of the engineers. I
am however not sure how committed they are to the Flashpaper platform, I
personally hope it'll survive the merger.
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 12:56
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
> because var
>
> Exactly.
>
>
> I believe that the content scrolling problem, which I
> described a couple of posts back, could be related to the
> code in the fix never executing. I'm not exactly sure, but
> the hitTest would seem to indicate something along these
> lines. Basically, I think there IS something called
> focusedComponent in the Flash Paper code, but the targeting
> in the fix is screwed up.
>
> -Jorge
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 7:48 am |
| I'm not 100% up to scratch on the whole allowDomain thing, but it does =
seem
that FP8 is much stricter than FP7, especially when it comes down to =
local
swf's. Also, I think that for FP8 you have to (or can choose to) specify
more granular access settings with regard to subdomains, etc.
Would be cool if there was a more condensed version of this article:
http://www.macromedia.com/devnet/fl...curity_print.h=
tml
I haven't found the time to dig into it
-Jorge
-----Original Message-----
Wrom: IVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDG
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan =
Richter
Sent: 27 March 2006 13:55
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
I get these securityerrors in the IDE only when I publish to Player 8. =
For
Player 7 it seems to works fine.=20
=20
If you place the published swf in the same domain as specified in
System.security.allowDomain does this mean that both published swf and
Flashpaper swf reside in the same domain? In that case I don't think =
you'd
even need System.security.allowDomain.=20
I wonder how the app would run if both swfs were under different domains =
and
accessed via Player 8...
See my other email for the reply on the trace issue.
Stefan
> -----Original Message-----
> Wrom: VCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBR
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Jorge=20
> Maiquez
> Sent: 27 March 2006 12:46
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> I find that the IDE locks up because a crazy amount of error msgs get=20
> displayed in the output panel when you try to load a remote flashpaper =
> into the (locally) published swf in the IDE. These msgs are of the=20
> form:
>=20
> *** Security Sandbox Violation ***
> SecurityDomain 'http://remoteFlashPaper.swf' tried to access=20
> incompatible context 'file:///C|/localPublishedFile.swf'
>=20
>=20
> This is resolved by placing the published swf on your webserver,=20
> within the allowed domain as defined by the=20
> System.security.allowDomain. Locally however, you will always get=20
> these msgs.. that is, I haven't found a way to supress them.
>=20
>=20
> Btw, did you manage to get a trace from within the onMouseDown of the=20
> Flash Paper fix?
>=20
> -Jorge
>=20
>=20
>=20
> -----Original Message-----
> Wrom: NVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKV
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan=20
> Richter
> Sent: 27 March 2006 13:13
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>=20
> I can also confirm that applying
> System.security.allowDomain("www.yourdomain.com");
> does indeed fix the hard crash when loading a Flashpaper from a full=20
> URL (yourdomain.cm specifies the URL where the Flashpaper is being=20
> loaded from).
>=20
> Stefan
>=20
> =20
>=20
> Of Stefan
> handler to
> to focus
> around, you'll
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training=20
> http://www.figleaf.com http://training.figleaf.com
>=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 7:48 am |
| > don't apply the fix then does the drag/hitTest problem still occur?
Yep, same prob.
> hit me offlist if you think it would be worthwhile
> following up with one of the engineers.
Yeah cool.. I'll do that. Although as you say, I'm not convinced it will get
me anywhere. After all, it has already been nearly 9 months since that fix
came out. And I too, hope Flash Paper will stick around.
-Jorge
-----Original Message-----
Wrom: ONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQ
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan Richter
Sent: 27 March 2006 14:06
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
I see.
When you try running your loaded FP and don't apply the fix then does the
drag/hitTest problem still occur?
You could be right and fixing one issue will bring up another...
I do have the original email from MM support somewhere, hit me offlist if
you think it would be worthwhile following up with one of the engineers. I
am however not sure how committed they are to the Flashpaper platform, I
personally hope it'll survive the merger.
Stefan
> -----Original Message-----
> Wrom: QWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQ
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 12:56
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
> because var
>
> Exactly.
>
>
> I believe that the content scrolling problem, which I described a
> couple of posts back, could be related to the code in the fix never
> executing. I'm not exactly sure, but the hitTest would seem to
> indicate something along these lines. Basically, I think there IS
> something called focusedComponent in the Flash Paper code, but the
> targeting in the fix is screwed up.
>
> -Jorge
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 7:48 am |
|
>
> Yep, same prob.
>
Then that may indicate that the 'fix' isn't introducing the drag issue you
are having and you may not need to be so concerned about the traces not
firing.
Stefan
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 11:57 pm |
| it may or it may not..
My beef with this fix is that the code was obviously written for a reason.
If it doesn't execute, then maybe it isn't fixing what it ought to fix. The
content scroll problem is related to focus management (Flash Paper doesn't
realise it doesn't have focus). Since the fix was supposed to solve an
inherent focus management problem with Flash Paper, it is a distinct
possibility that a working version of the fix could sort this as well.
-Jorge
-----Original Message-----
Wrom: HDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJB
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan Richter
Sent: 27 March 2006 14:35
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
>
> Yep, same prob.
>
Then that may indicate that the 'fix' isn't introducing the drag issue you
are having and you may not need to be so concerned about the traces not
firing.
Stefan
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 11:57 pm |
| But the fix *is* working, else I wouldn't be deploying it. It fixes the
dropped click events which were caused by the focus management getting
screwed. The fact that the part of code doesn't run in your tests may or may
not be intentional. For now I think it's intentional and it will run under
certain circumstances, circumstances which we have not yet encountered. A
try catch rarely runs but that doesn't mean it's not needed or working.
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 14:54
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
> it may or it may not..
>
> My beef with this fix is that the code was obviously written
> for a reason.
> If it doesn't execute, then maybe it isn't fixing what it
> ought to fix. The content scroll problem is related to focus
> management (Flash Paper doesn't realise it doesn't have
> focus). Since the fix was supposed to solve an inherent focus
> management problem with Flash Paper, it is a distinct
> possibility that a working version of the fix could sort this as well.
>
> -Jorge
>
>
>
> -----Original Message-----
> Wrom: HDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJB
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> Stefan Richter
> Sent: 27 March 2006 14:35
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
>
> still occur?
>
> Then that may indicate that the 'fix' isn't introducing the
> drag issue you are having and you may not need to be so
> concerned about the traces not firing.
>
> Stefan
>
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 11:57 pm |
| > For now I think it's intentional and it will
> run under certain circumstances, circumstances
> which we have not yet encountered.
That's where we'll have to agree to disagree. I have tried *a lot* of
things, and it NEVER fires. Trace out the vars that are in the _global
scope, you'll see what I mean.. I do admire your confidence in this code
though.. sometimes blind faith is the answer ;)
> A try catch rarely runs but that doesn't
> mean it's not needed or working.
That's not the same thing. I know try/catch does what it should. I can give
you examples showing a "working" try/catch situation. But can you give me an
example where the code in the fix does run? ... and that's the difference.
-----Original Message-----
Wrom: SCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXX
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan Richter
Sent: 27 March 2006 16:03
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
But the fix *is* working, else I wouldn't be deploying it. It fixes the
dropped click events which were caused by the focus management getting
screwed. The fact that the part of code doesn't run in your tests may or may
not be intentional. For now I think it's intentional and it will run under
certain circumstances, circumstances which we have not yet encountered. A
try catch rarely runs but that doesn't mean it's not needed or working.
Stefan
> -----Original Message-----
> Wrom: IMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYL
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 14:54
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
> it may or it may not..
>
> My beef with this fix is that the code was obviously written for a
> reason.
> If it doesn't execute, then maybe it isn't fixing what it ought to
> fix. The content scroll problem is related to focus management (Flash
> Paper doesn't realise it doesn't have focus). Since the fix was
> supposed to solve an inherent focus management problem with Flash
> Paper, it is a distinct possibility that a working version of the fix
> could sort this as well.
>
> -Jorge
>
>
>
> -----Original Message-----
> Wrom: HDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJB
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan
> Richter
> Sent: 27 March 2006 14:35
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
>
> still occur?
>
> Then that may indicate that the 'fix' isn't introducing the drag issue
> you are having and you may not need to be so concerned about the
> traces not firing.
>
> Stefan
>
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-03-27, 11:57 pm |
| No I can't give you that example - but the author of the code probably
could.
Firing or not, the code works and it fixes the bug it's meant to fix. The
fact that it never fires is something I can live with :-)
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 15:22
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
>
> That's where we'll have to agree to disagree. I have tried *a
> lot* of things, and it NEVER fires. Trace out the vars that
> are in the _global scope, you'll see what I mean.. I do
> admire your confidence in this code though.. sometimes blind
> faith is the answer ;)
>
>
> That's not the same thing. I know try/catch does what it
> should. I can give you examples showing a "working" try/catch
> situation. But can you give me an example where the code in
> the fix does run? ... and that's the difference.
>
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane. 2006-03-27, 11:57 pm |
| fair enough
-----Original Message-----
Wrom: TQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJ
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan Richter
Sent: 27 March 2006 16:43
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] Flash Paper bug fix
No I can't give you that example - but the author of the code probably
could.
Firing or not, the code works and it fixes the bug it's meant to fix. The
fact that it never fires is something I can live with :-)
Stefan
> -----Original Message-----
> Wrom: VTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVW
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Sent: 27 March 2006 15:22
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Flash Paper bug fix
>
>
> That's where we'll have to agree to disagree. I have tried *a
> lot* of things, and it NEVER fires. Trace out the vars that are in the
> _global scope, you'll see what I mean.. I do admire your confidence in
> this code though.. sometimes blind faith is the answer ;)
>
>
> That's not the same thing. I know try/catch does what it should. I can
> give you examples showing a "working" try/catch situation. But can you
> give me an example where the code in the fix does run? ... and that's
> the difference.
>
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training http://www.figleaf.com
http://training.figleaf.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
|
|
|
|
|