Ok, I guess that's it. I was confused by the new paragraph in that frame, maybe was meant to be in the previous frame.
Printable View
Ok, I guess that's it. I was confused by the new paragraph in that frame, maybe was meant to be in the previous frame.
Yeah, I cloned the frame and add the part, but I guess it's clear that it shouldn't be targeting a wrong group if the original isn't present BUT another type of object is.
It basically saw that one object that is part of the group was there, but since it wasn't an Active it targeted an Active that had a group, but for some reason it goes specifically for Group.Good.
It could be something between these two qualifiers specifically, or each qualifier can be confused by another specific, like each one have a douplelganger or something...
Makes me wonder if this could be exploited to do something useful, but it's most likely to only cause trouble and confusion.
The final frame illustrates that if there is an object with the right qualifier of the same type it supposed to be (from the global event), it works like it should. Same if you don't have any object of the wrong type in the right qualifier.
The problem is the one I mentioned. When Group.Texts was imported initially in the global events, it was associated with the Active Object type. Not sure why it associates it with the Active object in the second frame but if you delete and reimport Group.Texts from the second frame it will work.
I'll try to work on this in a future update.
Ah I see, didn't knew it was related, it feels a bit different but makes sense.
It's not a huge problem but can cause a lot of confusion and possibly break stuff that is added later.
But take your time, I'll mention this whenever people have this issue, I'm honestly more curious of what's next in the "wish/bug list", hope to see more new great stuff coming to Fusion whenever possible :D
Since we're here, here's a truly simple suggestion: Sign operation, that thing that returns 1 or -1, it goes like this: value / abs(value)
I use qualifiers of different types in global events all the time. Just this week I created an event that used about 8 versions of the same qualifier! (active, string, counter, button, list object, etc.). I've found that in these situations, a good practice is to make the event in frame events (where you can see clearly which types are which) and then copy them to global events when done.
Attachment 30781Attachment 30781Attachment 30782
Counter color doesn't work. What's going on?
That does seem like a bug. Though using the RGB coefficient method works:Quote:
Originally Posted by wuxuechen
https://bit.ly/3nrqFYp
https://bit.ly/30AlYCx
Active object : Replace Color and RGB Coefficient not work for android.
Attachment 30783
Your RGB coefficient is 0,0,0 it should be 255,255,255.Quote:
Originally Posted by wuxuechen
This is a limitation of the Android runtime, those features are not implemented on this platform.Quote:
Originally Posted by pradeep