*Originally posted by deamothul *
**hiya peeps, i just wanted to mention i experienced some strange behaviors too in fmx2004.
when i sometimes cut and paste a some flash mx code in fmx2004, flash doesn’t do anything. when i then save the file as flash mx , the effect shows up. when i then again save as flash mx 2004, It does work , very strange.
and i gotta say i love the OOP in AS 2 but i really hate the panel layout.
anywayz , good info here **
What OS are you running with?
Also are you copying frames or just the AS text?
Thanx,
-Ken
*Originally posted by ktoley *
**
Also if you already have the 30 day trial and chose to update, Macromedia will extend your trial for 30 additional days. **
hey, thats spiffy. Looks like I’ll be able to keep the trial going til the new machine arrives afterall
*Originally posted by senocular *
**hey, thats spiffy. Looks like I’ll be able to keep the trial going til the new machine arrives afterall **
Yup, go for it! We would prefer you evaluate the products based on their updated versions. And please post feedback on the products after you have installed the update. That is the best way to keep things improving.
Well I preordered the full versions the day they were available to do so Ive had them for a while. I just don’t trust the activation nonsense to install it on the current workstation and then the new one (which should be installed before the end of the year). That just gives me the opportunity to use them a little more for the purpose of familiarity when I do finally get around to using/installing MX04 “for real.”
Annoyance: Clicking on the current document tab when Flash is not the currently focused application will not make Flash the curently focused application. Atleast not the first time. It can take 2 (or more) clicks to actually focus Flash.
I have developed a pretty complex presentation which combines video and synchronized slides. The way the presentation works is like this:
The presenation is broken down into sections. Within each section are 6 videos and 6 slides. Each video is synched to the cooresponding slide. Once the video plays and reaches the end it should go to the next video/slide.
This functionality plays fine on Windows 2000 and XP, but does not work seem to work correctly under Windows 98 or ME. Once the video plays through it fails to go to the next video/slide.
Similarly, at the end of the 6th (and final) video in the section it should load the next section in the presentation. This also fails to work under Windows 98 or ME.
The presentation is built based upon the Flash MX 2004 Professional “Forms” template. Each video/slide is it’s own screen. The videos are using LabeledCuePoint navigation pointed at the main parent slide which hides/shows each video/slide screen.
If anyone has a work around or any knowledge as to what could be causing the problem I would GREATLY appreciate your help!
click “Skip Opening” at the beginning of the presentation
This brings you to the Main Menu.
Click on the top Photo.
This brings you to the Overview section.
Click on “Slide 01” from the navigation on the left side.
This starts the presentation. The video and slide should load and begin to play.
The problem occurs (on Win 98/ME machines) at the end of the first video. What SHOULD occur is the second video and slide loads and begin to play.
The other, similar problem, can be observed if you click on “Slide 06” and let the video play. At the end of the video it should load the “Roundtable” section of the presentation.
Once again ANY HELP or INSIGHT will be GREATLY appreciated.
Hey there just thought I would let you know that you aren’t the only one who has those crashes… i wasn’t sure what was causing it but I just missed a button on the toolbar(it was the first thing I went to when my comp booted up) and sure enough my whole system locked. I sent a report to macromedia too. Seems like if they could reproduce it they would have surely missed a button a few times in testing. Oh well,
I just loaded up Flash MX 2004 pro and I guess I had never tried it except by accident. When the opening dialog(I still have it come up, but I don’t think its of any consequence, just framing when I did it) popped up, I just moved over to the toolbar and clicked on the toolbar a few times next to an object that I figured it wouldn’t register as being close enough… Sure enough, with my computer, I had alienautopsy(provided with Alienware computers that catches crashes and notifies Alienware tech support) on and it told me that flash crashed and needed to be closed. So there’s my recreation of the whole deal.
I would be very greatful to anyone that would help this matter out and try to recreate this occurence so Macromedia can address it and solve it in a future patch. Thank you so much. I’ve enjoyed being a part of this forum and community and I am planning to start being a contributor in the near future. Take care.
Just wanted to ask if anyone had problems when using imported Swift 3D animations with MX2004. It doesn’t seem to work as good as it does with MX. For example, on my site I use Swift3D for the backgrounds in each section of my site. While in the development stages, I would place other content on layers above the 3D animation in different points in time. However, when I would test the movie only the background layer with the 3D animation would play, and none of the other content would show. But when I placed all the content at the same point in time as the background, everything shows up. I found a work around, but it limits my creativity with Swift3d. I wondered if anyone else experienced this type of problem. Let me know what you think. By the way my website is www.aroundaway.com. Thanks.
FORMS: At first they seemed like a great thing: you could show a splash / enter while your main movie loads invisibly into another form. And it works like that too…Except
your main movie will load and appear in the range of 500 or so pixels (or miles) to the left (or the right, or halfway off the stage) from where you originally authored it.
Forms have an ‘autosnap’, which after a good 2 months of studying it, actually doesn’t do anything but make your loaded material appear even further away.
Nothing I’ve found yet can make a loaded swf appear in a Form in the desired location.
1 - make an mc on a Form.
2 - export it from the lib.
3 - load that mc into the Form.
4 - it loads in at a different place every time you test the movie.
Tonight I wished the guy who invented Forms was in my house so I could punch him.
sorry for the interupt, i have also noticed bitmap distortion in another situation
Okay, here is the pickle
[color=black][font=Arial]
[/font][font=Verdana]because i am publishing the swf to fit exact in the browser window with flash, and if the swf does not match the exact size of the browser window a horizontal or vertical stretch causes the bitmaps to distort (as in not just a aspect ratio type distort as in jagged edges on all smooth crisp lines kind of distortion), leaving the vectors smoothly stretched due to there nature: i have never used anything but flash mx 2004 so i don’t know if this is a new bug or what, but i would figure that the “exact fit in a browser” option flash gives you would create more desirable results[/font][/color]
We did some more research and it’s a little known fact but in certain scenarios version2 components kill normal buttons behaviors and textfields. They do not interoperate with them. If you use version 2 components on your flash movie, you cannot use any manually created buttons/button symbols or text fields. The version 2 components’ Focus Manager basically tries to take over all focus handling, so naturally this messes up the intrinsic behavior of aforementioned buttons and text fields.
In your case, it’s the clicking of the asfunction line or link that is setting focus into the TextArea component. Then textarea component keeps stealing the focus back, thus your buttons stops functioning unless you double click on it or move the mouse cursor and click on the button. Such actions(double-click and mouse movement) momentarily take’s the focus away from the textArea component.
An escalation bug has already been filed regarding this issue with our engineering. Unfortunately we don’t know when they will release a patch for this issue.
A Workaround I can suggest to resolve the issue is to use a version2 component like the button component but which I guarantee would resolve your issue, although the look and feel of the component button may not fit your design but it’s functional. Some people don’t want to do that for visual reasons.
**