RE: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
I second this. The problems I had all went away after I got rid of the config files for prior versions of FB. You might also try starting FB with the -clean option. In the flexbuilder.ini file (or the eclipse.ini file if you're using the FB plug-in), insert -clean as the first line and save the file. Restart flex builder. HTH, ~randy _ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Williams Sent: Tuesday, April 01, 2008 4:53 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems this is how I did it. create a new project in 3 final. then copy the code I’d written in 3 beta and assets into new project. the problem I had was with the files in the old project that aren’t code (configs n stuff) Glenn From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Schultheiss Sent: Tuesday, April 01, 2008 10:49 AM To: [EMAIL PROTECTED] Subject: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems My developers are also complaining that their 'and my' applications have broken since Beta 3 to the Final release. This has hit me unexpectedly as I did not test. On top of that I have deadlines to meet this week. Is there a doc i can refer to get a complete list of changes.. What's the best way to roll back to beta 3, at least so i can get these next presentations out the door. --- In HYPERLINK mailto:flexcoders%40yahoogroups.com[EMAIL PROTECTED], a3leggeddog_-ca [EMAIL PROTECTED] wrote: This application is somewhat unusual in that we dynamically create components in accordance with a user defined XML file. We switched from BETA 3 Milestone 4 to the new released GA version of Flex. The anomolies that we are seeing are in multiple areas. The most evident are in the initial creation of widgets. We use an Accordion component and programatically introduce child panels with textboxes, comboboxes, etc. The comboboxes are tied to ArrayCollections dynamically derived from web service calls. Everything worked fine in BETA but when we switched, all hell broke loose. 1) The Headers for the 2nd Accordion panel (there are two total) is now off the screen 2) There now appears a vertical scroll bar, where there was none in the BETA version 3) When attempting to select the 2nd panel, via the header, it does not open the panel the first time. Disappears from view and we have to scroll down to it and click the header again, at which time it now selects the 2nd panel appopriately. 4) There are items in the comboboxes, but when I click tje button to expose the dropdown the program starts behaving erraticly. It will select another item, but the response becomes extremely slow and eventually memory usage goes way up, the fan comes on and the screen will eventually lock up 5) On the comboboxes which I have a typeahead programmed (after 3 characters the component automatically calls a web service to provide content via a database call). The content comes back, but the behavior is different than it was during BETA. It should display a dropdown list allowing the user to choose the corect content. It now selects the first item in the list and does not display the dropdown. The behavior that I am seeing is different across the board, from BETA to the new release version. It often ends up in some race condition where it eats up memory and eventually stops responding and needs to be force quit. No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.3/1354 - Release Date: 4/1/2008 5:38 AM image001.png
RE: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
this is how I did it. create a new project in 3 final. then copy the code I'd written in 3 beta and assets into new project. the problem I had was with the files in the old project that aren't code (configs n stuff) Glenn From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Schultheiss Sent: Tuesday, April 01, 2008 10:49 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems My developers are also complaining that their 'and my' applications have broken since Beta 3 to the Final release. This has hit me unexpectedly as I did not test. On top of that I have deadlines to meet this week. Is there a doc i can refer to get a complete list of changes.. What's the best way to roll back to beta 3, at least so i can get these next presentations out the door. --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com , a3leggeddog_ca [EMAIL PROTECTED] wrote: This application is somewhat unusual in that we dynamically create components in accordance with a user defined XML file. We switched from BETA 3 Milestone 4 to the new released GA version of Flex. The anomolies that we are seeing are in multiple areas. The most evident are in the initial creation of widgets. We use an Accordion component and programatically introduce child panels with textboxes, comboboxes, etc. The comboboxes are tied to ArrayCollections dynamically derived from web service calls. Everything worked fine in BETA but when we switched, all hell broke loose. 1) The Headers for the 2nd Accordion panel (there are two total) is now off the screen 2) There now appears a vertical scroll bar, where there was none in the BETA version 3) When attempting to select the 2nd panel, via the header, it does not open the panel the first time. Disappears from view and we have to scroll down to it and click the header again, at which time it now selects the 2nd panel appopriately. 4) There are items in the comboboxes, but when I click tje button to expose the dropdown the program starts behaving erraticly. It will select another item, but the response becomes extremely slow and eventually memory usage goes way up, the fan comes on and the screen will eventually lock up 5) On the comboboxes which I have a typeahead programmed (after 3 characters the component automatically calls a web service to provide content via a database call). The content comes back, but the behavior is different than it was during BETA. It should display a dropdown list allowing the user to choose the corect content. It now selects the first item in the list and does not display the dropdown. The behavior that I am seeing is different across the board, from BETA to the new release version. It often ends up in some race condition where it eats up memory and eventually stops responding and needs to be force quit. image001.png
Re: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
On Sunday 30 Mar 2008, a3leggeddog_ca wrote: comboboxes are tied to ArrayCollections dynamically derived from web service calls. Everything worked fine in BETA but when we switched, all hell broke loose. If you post your test case code here people will be more able to help. -- Tom Chiverton Helping to vitalistically differentiate internet customers on: http://thefalken.livejournal.com This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at Halliwells LLP, 3 Hardman Square, Spinningfields, Manchester, M3 3EB. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by The Solicitors Regulation Authority. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 2500. For more information about Halliwells LLP visit www.halliwells.com. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
[flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
My developers are also complaining that their 'and my' applications have broken since Beta 3 to the Final release. This has hit me unexpectedly as I did not test. On top of that I have deadlines to meet this week. Is there a doc i can refer to get a complete list of changes.. What's the best way to roll back to beta 3, at least so i can get these next presentations out the door. --- In flexcoders@yahoogroups.com, a3leggeddog_ca [EMAIL PROTECTED] wrote: This application is somewhat unusual in that we dynamically create components in accordance with a user defined XML file. We switched from BETA 3 Milestone 4 to the new released GA version of Flex. The anomolies that we are seeing are in multiple areas. The most evident are in the initial creation of widgets. We use an Accordion component and programatically introduce child panels with textboxes, comboboxes, etc. The comboboxes are tied to ArrayCollections dynamically derived from web service calls. Everything worked fine in BETA but when we switched, all hell broke loose. 1) The Headers for the 2nd Accordion panel (there are two total) is now off the screen 2) There now appears a vertical scroll bar, where there was none in the BETA version 3) When attempting to select the 2nd panel, via the header, it does not open the panel the first time. Disappears from view and we have to scroll down to it and click the header again, at which time it now selects the 2nd panel appopriately. 4) There are items in the comboboxes, but when I click tje button to expose the dropdown the program starts behaving erraticly. It will select another item, but the response becomes extremely slow and eventually memory usage goes way up, the fan comes on and the screen will eventually lock up 5) On the comboboxes which I have a typeahead programmed (after 3 characters the component automatically calls a web service to provide content via a database call). The content comes back, but the behavior is different than it was during BETA. It should display a dropdown list allowing the user to choose the corect content. It now selects the first item in the list and does not display the dropdown. The behavior that I am seeing is different across the board, from BETA to the new release version. It often ends up in some race condition where it eats up memory and eventually stops responding and needs to be force quit.
[flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
I third this the only way i got up and running correctly was to purge my old workspace (rename it before opening FB) - that way it builds a new workspace and everything has run fine since. Mitch --- In flexcoders@yahoogroups.com, Randy Martin [EMAIL PROTECTED] wrote: I second this. The problems I had all went away after I got rid of the config files for prior versions of FB. You might also try starting FB with the -clean option. In the flexbuilder.ini file (or the eclipse.ini file if you're using the FB plug-in), insert -clean as the first line and save the file. Restart flex builder. HTH, ~randy _ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Williams Sent: Tuesday, April 01, 2008 4:53 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems this is how I did it. create a new project in 3 final. then copy the code I'd written in 3 beta and assets into new project. the problem I had was with the files in the old project that aren't code (configs n stuff) Glenn From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Schultheiss Sent: Tuesday, April 01, 2008 10:49 AM To: [EMAIL PROTECTED] Subject: [flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems My developers are also complaining that their 'and my' applications have broken since Beta 3 to the Final release. This has hit me unexpectedly as I did not test. On top of that I have deadlines to meet this week. Is there a doc i can refer to get a complete list of changes.. What's the best way to roll back to beta 3, at least so i can get these next presentations out the door. --- In HYPERLINK mailto:flexcoders%40yahoogroups.com[EMAIL PROTECTED], a3leggeddog_-ca seth@ wrote: This application is somewhat unusual in that we dynamically create components in accordance with a user defined XML file. We switched from BETA 3 Milestone 4 to the new released GA version of Flex. The anomolies that we are seeing are in multiple areas. The most evident are in the initial creation of widgets. We use an Accordion component and programatically introduce child panels with textboxes, comboboxes, etc. The comboboxes are tied to ArrayCollections dynamically derived from web service calls. Everything worked fine in BETA but when we switched, all hell broke loose. 1) The Headers for the 2nd Accordion panel (there are two total) is now off the screen 2) There now appears a vertical scroll bar, where there was none in the BETA version 3) When attempting to select the 2nd panel, via the header, it does not open the panel the first time. Disappears from view and we have to scroll down to it and click the header again, at which time it now selects the 2nd panel appopriately. 4) There are items in the comboboxes, but when I click tje button to expose the dropdown the program starts behaving erraticly. It will select another item, but the response becomes extremely slow and eventually memory usage goes way up, the fan comes on and the screen will eventually lock up 5) On the comboboxes which I have a typeahead programmed (after 3 characters the component automatically calls a web service to provide content via a database call). The content comes back, but the behavior is different than it was during BETA. It should display a dropdown list allowing the user to choose the corect content. It now selects the first item in the list and does not display the dropdown. The behavior that I am seeing is different across the board, from BETA to the new release version. It often ends up in some race condition where it eats up memory and eventually stops responding and needs to be force quit. No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.3/1354 - Release Date: 4/1/2008 5:38 AM
[flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
This application is somewhat unusual in that we dynamically create components in accordance with a user defined XML file. We switched from BETA 3 Milestone 4 to the new released GA version of Flex. The anomolies that we are seeing are in multiple areas. The most evident are in the initial creation of widgets. We use an Accordion component and programatically introduce child panels with textboxes, comboboxes, etc. The comboboxes are tied to ArrayCollections dynamically derived from web service calls. Everything worked fine in BETA but when we switched, all hell broke loose. 1) The Headers for the 2nd Accordion panel (there are two total) is now off the screen 2) There now appears a vertical scroll bar, where there was none in the BETA version 3) When attempting to select the 2nd panel, via the header, it does not open the panel the first time. Disappears from view and we have to scroll down to it and click the header again, at which time it now selects the 2nd panel appopriately. 4) There are items in the comboboxes, but when I click tje button to expose the dropdown the program starts behaving erraticly. It will select another item, but the response becomes extremely slow and eventually memory usage goes way up, the fan comes on and the screen will eventually lock up 5) On the comboboxes which I have a typeahead programmed (after 3 characters the component automatically calls a web service to provide content via a database call). The content comes back, but the behavior is different than it was during BETA. It should display a dropdown list allowing the user to choose the corect content. It now selects the first item in the list and does not display the dropdown. The behavior that I am seeing is different across the board, from BETA to the new release version. It often ends up in some race condition where it eats up memory and eventually stops responding and needs to be force quit.
[flexcoders] Re: Flex Beta 3 to Flex 3 Migration Problems
The major functional problem so far is a change to ComboBox behaviour - now it respects selectedItem property. In Flex2 if selectedItem was set to null it was selecting the first item. Now it stays clear. Yes, this this a proper behaviour, but it breaks the code if you try to reach selectedItem property without checking it. Previously it was filled in automatically for you. Unfortunately, Adobe does not respect the fact that improvements of the SDK breaks the existing code. I submitted a bug in Flex2 regarding list selection indices order. It was fixed in next release without any mentioning about it in the release notes. Of course it immediately caused a crash of ab application which relied on the order of selection. I wonder what will Adobe do if it come across with tm.tm_mday structure. This is really tempting to fix! :)) PS And I an not mentioning The Panel problem :) Cheers! --- In flexcoders@yahoogroups.com, Joan Lafferty [EMAIL PROTECTED] wrote: Hi Seth, Unfortunately, we don't have this list. I tried to use our bugbase to find the bugs fixed from Beta 3 to release and that proved futile as well. So, I looked through all of our changelists and didn't see any that were obvious changes to Accordion and ComboBoxes. There were many changes to fix bugs in our AIR components, DragManager, and List Components though. Can you be more specific as to what some of your problems were during this migration? Were you using AIR? If you can provide a sample of your code, that could help a lot. Thanks, Joan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of a3leggeddog_ca Sent: Thursday, March 20, 2008 2:31 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Flex Beta 3 to Flex 3 Migration Problems Hi - We are having significant problems after migrating between Beta 3 and the GA release. Differences in the accordion component, comboboxes, spacing, control focus, etc. Has anyone else had these problems? Is there a list of the things that changed between Beta 3 and the final release? HELP!! Thanks, Seth
