do you really think it's good practice for a company to NOT allow their customers to switch back to a prior version in case of a bug in the release? that's just downright shady, especially since we paid for the software.
--- In [email protected], "hgnowhg" <hgno...@...> wrote: > > Actually, not really. I completely disagree. The flex evangelists (there are > many of them!) are really good at hyping up a product and not pointing out > the limitations. Why should a datagrid crash when it is given data? Please > enlighten me. I was in no way depending on the beta version for my final > project. It is the non-beta (read: Paid-version) that is causing us so much > grief! > > --- In [email protected], "bobleisle" <bleisle@> wrote: > > > > Hi, > > > > With all due respect, the situation you've described is not so much an > > argument for taking a pass on FlashBuilder4, but rather a really good > > argument for not depending on beta level development software for paying > > work. It's in beta for a reason. > > > > > > > > --- In [email protected], "hgnowhg" <hgnowhg@> wrote: > > > > > > Just a word of caution to anyone thinking of upgrading to Flex 4 from the > > > beta version: You will NOT be able to go back. Once your beta license > > > expires, you're done! My coworker's beta license just ended and he's been > > > searching ALL day for the past 2 days for a way to get around this. Adobe > > > USED to provide a way to extend the beta license but since the new > > > version is out they don't offer a way to do this anymore. If you're still > > > on Flex 3, STAY ON FLEX 3! Why? We've both imported projects from the > > > beta version to our new Flash Builder 4 version and have found many > > > things that are acting weird (like what I post below and what my coworker > > > filed yesterday or the day before on this forum). We're on a tight > > > deadline and now we're screwed. Flex 3 doesn't provide the full features > > > we put in our app, Flash builder 4 is messed up and the beta version says > > > his license expired. I have a few days on mine but not holding out hope > > > on Adobe to fix the issues soon (as evidence that Flex 4 Beta was in beta > > > version for a year!). Wait until Flex 5 to upgrade to Flex 4! > > > > > > > > > --- In [email protected], "hgnowhg" <hgnowhg@> wrote: > > > > > > > > just tried it in the beta version and everything works fine. what did > > > > adobe do that messed this up? > > > > > > > > --- In [email protected], "hgnowhg" <hgnowhg@> wrote: > > > > > > > > > > I just upgraded to flash builder 4 from the beta version. I imported > > > > > my project and now my datagrid is acting funny. I have data paging > > > > > enabled. The one thing I tweaked was on this part: > > > > > http://sujitreddyg.files.wordpress.com/2009/06/165.png > > > > > > > > > > Instead of setting the "Count operation" to "count()", I've set it to > > > > > "None". I have a large amount of data and setting it to "None" makes > > > > > the thumb larger so that users can use it. It also disables the > > > > > ability to "jump" pages (which uses a lot of memory if you have a > > > > > datagrid). > > > > > > > > > > Everything worked fine in the beta version of flash builder but in > > > > > the non-beta version I came across a problem: I can initially page > > > > > (with my mouse wheel) a few times and then it just stops for no > > > > > reason. I try to keep scrolling w/ the mouse wheel and nothing. > > > > > However, if I click on a row, then it will get another page. I have > > > > > to continue to click on the rows in order to get another page. > > > > > Annoying, to say the least. > > > > > > > > > > Anyone notice this? I didn't change anything so figured it must be > > > > > the updated version. (You can see for yourself w/ your own > > > > > project...just change the Count operation to "none" and then try to > > > > > page through the datagrid).....any suggestions? > > > > > > > > > > > > > > >
