I know this, but as I already migrated my old code to support v2 reference points and code ranges, I don’t want to go to compatibility mode anymore. It was easier to migrate the old widget.lua to remove reference points as they didn’t break scrollView.
But this is side issue, the original issue is v2 scrollView breaking other element translationTo:s
Widgets with G2.0 should be fully compliant with G2.0 positioning methods.
I’m having this issue too. Not only if an element is scrolled inside a scrollview (for example, loading images inside the scrollview rotating with transition.to) but also on other occasions too (that I’m still trying to figure out).
What did you really did “matti.paalanen”? Because I already have “graphicsCompatibility = 1” but it still doesn’t work.
Does it have anything to do with the “onComplete” not being called?
What I did was that I downloaded the published version of the old widgets code and saved it as a distinct lua file into my project. Then I edited it by commenting out all the references to setReferencePoint calls.
I don’t use the compatibility mode in my project because otherwise I already migrated to 2.0
So I just manually changed the widget imports to use this modified 1.0 lua file instead of the official widget library and now everything works ok.
I can’t upgrade mine now but, I found a solution for the scrollview:
function fix.transition.to(target, params) if (params and params["onComplete"] and (not params["onPause"])) then params.onPause=function() transition.resume(target) end end return transition.to(target, params) end
It seems that scrollview pauses the transitions of it’s childs when moved and so, all that I need to do is call resume on pause for that case.
But I’m still having problems with another things and transitions. There are situations when sometimes, when I click on a button that slides 2 groups from right to left, the slide stops (and some other animations not related to it stop too) or the loading images that come inside these groups stop rotating.
This is weird because it only happens sometimes and also stops some animations that are not related.
Ok, I solved that. I was using a recursive function to spin the loadings and the only change I made was make it local instead of global to self image element. Now I use the fix I post before on every transition and it works for me =).
Has anyone filed a bug report on this? If not, can some file one please?
And please post the bug number back to this thread. You might want to include a link to the thread in the bug report.
Thanks
Rob
Well, I don’t know if it is a but or not because it makes a little sense to pause transitions when they are not visible. But they should be resumed when they become visible again I think.
I would agree that pausing them when off screen makes sense from that perspective, but not resuming them when they come back on screen still seems like a bug. If we want engineering to look at it, they will need a bug report.
Thanks
Rob
I submitted it as a bug. It’s the first time that I did that and so, I don’t know if it is ok but, I think it is.
Thanks for the information! Hopefully we’ll get a bugfix soon
This was fixed in daily build 2088.
Rob
Ah ok, good to know thanks!
As I don’t yet have subscription to daily builds, is there any rule of thumb, how long is the official version update cycle if it contains these kinds of bugs?
We don’t have a set schedule on when we release new public builds. There are many circumstances that drive when. But in this case with Graphics 2.0 being so big of a change and some other fixes that impact many people, we will likely have a new build sooner than later, but I can’t commit to a time.
Rob
But matti.paalanen, I believe that you can use my fix on 2013.2078. At least I’m using it without any problem. Unless you really need to use the “pause” callback for anything else. But for the most cases, the fix should work =).
Hi guys,
i’m facing the same issue with the current version. I have an animating image (that isnt attached to the scroll view). It can animate perfectly if i didnt scroll the scrollview. When i scroll it, the animation hangs.
Solutions tried:
1)I tried resuming the animations by calling transition.resume() at the scrollview listener but it still doesnt work.
2)I tried attaching the animating image to the scrollview and it didnt work either.
3)Lastly i tried setting graphicsCompatibility as 1 but it still doesnt work.
Any help is appreciated, thanks!
Regards,
Vince
Can you produce a minimal sample app that reproduces the problem? Make sure you put it in a .zip file (no other format) and include the build.settings, config.lua and an assets like images needed to run the sample.
The please file a bug report using the “Report a Bug” feature at the top of the page.
Thanks
Rob
Hi Rob,
I managed to fix the bug, realize it’s a mistake on my side because the scrollView i used was a plugin from the community called “widgetFix”. The scrollview from that widget isn’t able to support animation properly. Nonetheless, thanks for looking into this!
Regards,
Vince
Hi guys,
i’m facing the same issue with the current version. I have an animating image (that isnt attached to the scroll view). It can animate perfectly if i didnt scroll the scrollview. When i scroll it, the animation hangs.
Solutions tried:
1)I tried resuming the animations by calling transition.resume() at the scrollview listener but it still doesnt work.
2)I tried attaching the animating image to the scrollview and it didnt work either.
3)Lastly i tried setting graphicsCompatibility as 1 but it still doesnt work.
Any help is appreciated, thanks!
Regards,
Vince
Can you produce a minimal sample app that reproduces the problem? Make sure you put it in a .zip file (no other format) and include the build.settings, config.lua and an assets like images needed to run the sample.
The please file a bug report using the “Report a Bug” feature at the top of the page.
Thanks
Rob