pacweb

I couldn’t find a way to delete the post. So I am closing the thread.

Hi Everyone,

I am back from Thanksgiving (a USA holiday). I am testing animations on a copy of my testing site that also has ACF installed. So far all the animations are working as they should.

@shoalinagent – I have a question or two that came up when I looked at the EA file. I will email you privately.

Is anyone running into any problems with ACF or any other issues?

Thanks,
~ Wayne

Hi,

@timm – sounds like a great plan. Even though there are quirks, I agree that getting more people testing would help. Then we can find more of the interesting quirks like @shoalinagent’s. It feels like there are more than a few versions of the plugin available, not just a production and a development version.

@shoalinagent – Timm brings up a good point, in Edge Animate are you assigning any CSS classes to your assets (images, shapes, etc)? Also, have you changed the attribute of any text assets from being a DIV to something else (h1, p, etc)?

Thanks!
~ PacWeb

Hi @shoalinagent,

That is weird. Advanced Custom Fields is The plugin for when you need a custom field. I will have to try installing it on a test site and see if I can get the same reaction.

The “stage size” message you are getting in the import confirmation, I get that all of the time. I am pretty sure Timm said it was harmless. But I think he is looking into it along with the responsive scaling issue.

Would you mind sending me an OAM of your animation?
I’d like to also test it with ACF. If you can’t share it, I totally understand.

Thanks,
~ PacWeb
info@pacificwebfoundry.com

@nolimit.ma and @manstok – thank you for posting your experiences. I got me thinking and I have been able to reproduce the over-enlargement issue I mentioned above.

I have setup 5 animations on a testing site: http://es-test.sfwebfoundry.com/

4 of the animations have the over-enlargement problem. I have tested them in most of the major browsers, and the issue has existed in all cases (possibly except 1): Chrome, Safari and Firefox for MAC; Chrome, Firefox, and IE for Windows; and Safari Mobile (iOS). These animations are all set in Edge Animate to use Responsive Scaling, but do not have a Max Width set. So they blow up all over the place. The 5th one (named Test #4 version 1) has the Max Width set and displays correctly.

BTW, if you check out the site, please keep in mind that Test #4 was only meant as a quick and dirty test animation (I admit it is awful looking) to explore this responsive scaling issue. Another thing to note, Test #4 is only 352×301.

These animations were made in the Nov update version of Adobe Edge Animate, CC 2014.11. I used the latest, test build of the Edge Suite plugin.

So it looks like the importing issues are gone, but there is this scaling issue. Thankfully setting a Max Width in Edge Animate has been a solid workaround.

~ PacWeb

Here is an update to the problem I found earlier and a solution …

It has been difficult to exactly reproduce the problem I saw yesterday. What I am seeing is that when Responsive Scaling is turned on in an animation, the stage becomes huge (proportionally) in the final webpage. The animation ends up bigger than what was built in Edge Animate. It is as if responsive scaling over scales the animation. For example, I built a test animation that was 550×353. When I inserted it into a page, the animation extended beyond my browser window, which was about 1400 by 720.

I found a simple fix for this problem:
make sure to set a Max Width for your stage, equal to the actual width of your stage.

Using my previous example above, when I set a max-width to 550, and re-uploaded the animation, the animation was the right size and exactly the same as in Edge Animate.

~ PacWeb