|
Hi Matt,
No they did not.
My Client's maintenance contract has expired and he has
tried to get it renewed and was told he'd be called back and never
was.
I must say he's pretty disappointed about the amount of
money he's paid out for Flex and what he's got in return.
I've now wasted what amounts to a solid week just trying to
get good code to work with a system that should just work.
I think I'm saying I'm disappointed as well. I want to say
that Flex is a fantastic product and it is except my clients service and
except for this bug which I just cannot find a workaround
for.
I've checked that the code does not have any binding
warnings - it does not. I've checked for the "dreaded NoChange bug" and it does
have this.
If Adobe are not going to fix this and release an update
for Flex 1.5 (and I think they should) they should at least spend some time
working out a workaround that WILL WORK.
I'm willing to supply my complete application source code
to Adobe if that would help.
Is there anything you can do to help or get any of the
other Adobe guys to help?
Or can anyone on Flexcoders help?
Libby has offered some help but I could not get any of her
suggestions to resolve the issue. I've also tried the "XWrapper" solution but
this cannot work in my case.
Regards,
Simon
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Chotin Sent: 09 May 2006 07:42 To: [email protected] Subject: RE: [flexcoders] Good Code Stops Working For Me Too Did they contact
you? Someone said they would I think. I don’t think we have
an existing fix for it though. Matt From:
Have support made any
response to this issue at all? I still have no
solution. Simon From:
I’ve forwarded this on
to our support team. It’s possible we have a hotfix for it already (or
they’ll know of a workaround or something). Matt From:
I have some MXML TitleWindow
components that have form field that are bound to their respective
VO's. These were working fine but when I
started implementing validation with the Validators components Binding stopped
working in these TitleWindow components. I have spent several days trying to
figure out what has gone wrong but I am certain that the code is
good. So I decided to duplicate the code,
so I created a new blank file and copied and paste the code into it. I'm using
cairngorm and it has a ViewHelper so I did the same with this. The code for the
new files is identical with the exception of the name changes for the MXML file
and the ViewHelper file. Now when I run the app, the
duplicated files work correctly and display the bound data. But the original
files are still not binding even though the new Component is running correctly
in the same app at the same time! I have read a post by Libby that
mentioned good code stops working and followed the response by Matt Chotin, but
am still unable to fix the problem (if its the same!). To Adobe/MM: If this is a bug in Flex 1.5, do
you intend to release an update for it? Simon -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- RE: [flexcoders] Good Code Stops Working For Me Too Simon Fifield
