No matter what I do even if I test an empty movie I get this warning, what am I supposed to do about this as timeline starts with 1 not 0, just be aware of it and get this every time I test something?
This is just an information to you that the easeljs handles frame numbers differently(starting from 0) than flash as3(there it starts from 1). You need to be aware of this in case if you are referring to frame numbers in your frame scripts in Canvas document.
Very annoying, would be good to have a button saying ok I get it do not warn me again
I agree that there should be an option in preferences to disable compatibility warnings. Having those warnings spew into the console every single time you publish no matter what just encourages people to ignore warnings altogether.
Guess this will eventually happen.
I bet it won't. If anything, they'll fix the timeline in Canvas mode so it shows the first frame as 0. Frame numbering is zero-based because that's how the CreateJS library works, and it works that way because zero-based indexing is simply faster and more elegant to code. Jamming a "+1" toggle in there would just impose a performance penalty for no real benefit.
is there any different between free trial animate cc and license cc? because i want to try publish and it says
"Frame numbers in EaselJS start at 0 instead of 1. For example, this affects gotoAndStop and gotoAndPlay calls. (3)"
what should i do? i still don't get it the anwer ??
There is no difference between trial and licensed copy of Animate with respect to Frame Numbers. As I have mentioned earlier it is displayed for your information in case if you are used to AS3 frame scripts where you refer frame numbers that starts from 1 where as in Canvas document it starts from 0.
In AS3, you write a frame script say gotoAndPlay(3) to go to and play frame #3
In Canvas, you need to use 2 in place of 3 to gotoAndPlay frame number 3
Unless you are adapting an already existing file, on new canvas projects, I found it best to give the frame a name and the reference it like: gotoAndPlay("framename") this way you do not have to worry which number it ends up being.
Just turn off "Show Output" in the output console. If you do end up getting what seem to be errors, turn it back on.
In a similar way, you can block all ads on web sites by turning off your monitor.
How do I resolve this problem?
Which problem is it that you need to resolve? If you're talking about the original topic, and how frame numbers start at 0, there isn't a problem. The message is for information, unless you have done gotoAndStop() or gotoAndPlay(). The message reminds you that if the timeline frame you want to go to is say 15, the correct gotoAndStop() for that would be gotoAndStop(14), one less than the number shown in the timeline.
Select frame, name in attribute (frame label)
Then jump to the Frame tab.
This is the recommended practice now.
I didn't really like to jump frames before.
Because it's not intuitive.
After the version becomes ANCC.
It feels like software is far from the public.
People who can't write code,
Basically not used.
Don't know what to call progress or retrogression
Flash is the most popular time,
Because anyone can use it,
As long as you open the software, not too much learning can make the job.
I think the best version is FLASH8.
Because his help was the friendliest.It's simple.
Now just blindly seeking to add functionality,
And forget who's using it.
Network animation Interactive Software.
Definitions have long been forgotten.
Animators know little about code.
The programmer doesn't use it.
I hope I can get the code assistant to do it and give the Help manual
Instead of chasing the popular.
Do not let people, for a small code to come here to ask.
I often get told to see JS to see Easejs.
But I don't even know what to look at.
This error code is a usability nightmare. It makes me wonder if the people at adobe ever use their own software.
It's like when someone poops on top of a wedding cake;
It doesn't matter how good the cake was, it's all garbage now.