Really nice looking interaction - you may want to share the .story file here so that others are able to test the file to come up with ideas on how to return it to the starting location based on your set up.
Thanks Solange for sharing that here - and although it's a lot of work, you did a great job with it! If you'd like to see the ability to use absolute positioning within your states I'd suggest submitting it as a feature request and reference this thread and project for how much easier it would be with that element.
5 Replies
Hi Solange,
Really nice looking interaction - you may want to share the .story file here so that others are able to test the file to come up with ideas on how to return it to the starting location based on your set up.
Thank you Ashley,
The best I could do so far is to move the arrow a little bit to the side so it looks better.
The problem that I still have is that then, the arrows "overlap" if more than one is dropped in the same box.
If anyone can find a solution I would be very happy.
See the code attached.
I made it work... but... It's a very painful process!
I had to calculate, for each label and each box, the number of pixel to move the label back to it's original position.
This means creating 7 states per label , plus one if the label is dropped outside a box. For a total of 64 states!
And then, for each drop possibilities, a trigger to change the state of the label to the appropriate one (64 triggers).
For example, label 1 dropped on box 5? change the state of label 1 to label1_box5_init!
This makes me wonder, WHY cant we have an option for absolute positioning in the state parameters?
It would make more sense to just set the label back to the original state once dropped to return it to it's original position.
Please, if you come up with a better solution I would love to know. My method is so time consuming I would not use it much.
If you are curious (and masochistic enough) to use this interaction... I've linked the story.
Note: I've attached the wrong file to this post. See the next post for the correct story.
and I can't remove those strange characters!
Normal 0 false false false oNotPromoteQF /> EN-US X-NONE X-NONE ontGrowAutofit /> ontFlipMirrorIndents />
Here's the correct story.
Thanks Solange for sharing that here - and although it's a lot of work, you did a great job with it! If you'd like to see the ability to use absolute positioning within your states I'd suggest submitting it as a feature request and reference this thread and project for how much easier it would be with that element.
This discussion is closed. You can start a new discussion or contact Articulate Support.