Drag the ellipse (starting color “grey” - set in Hype interface) onto the rectangle - it turns red (class “dropped”).
Drag the ellipse off the rectangle it turns green (class “droppedAndMoved”).
Details
The CSS (class) is set in “HTML Head”. Function “hitCheck” does the work.
In the code the rectangle is given an ID of “dropTarget”; the ellipse is simply referenced as the “element”.
Note: If You just wanted the ellipse turned back to grey (original color set in Hype) you will not need the “droppedAndMoved” class (green color) in the CSS or the “droppedAndMoved” add/remove class code in the “hitCheck” function.
Given you have a worked with dragging in Hype before the JS needed to add and remove a class can be found here … basically all you need is to do the following commands:
You superstars, both of you! I’m checking out all you’ve posted right now!
@MaxZieb, I was having a look at the classList side of things earlier today but I obviously wasn’t implementing it properly. I’ll study it all more closely.
And @JimScott, thank you so much for your demo… I’m keenly investigating it even as I type!
Just a quick (although who knows ) extra question… is there a relatively simple way to target the classes that have changed and return them to their original class when a scene reloads?
I can’t seem to get the changed classes to ‘respond’ to anything.
I’ve been trying hard but getting nowhere for ages. Hope you can help shed some light
Overview
This demo is slightly different in the set-up than my previous version...
There are now two scenes:
Scene 1
There are two elements now to drag on to the target square; and there is only one type of class change - from the original color to the new color (red) when moved on to the target square. When moving the element(s) out of the square they revert to their original color.
Scene 2
Basic scene with a back button to Scene 1.
New function "resetClasses"
Uses "querySelectorAll" to create a list all the elements with the class name "dropped".
A "for loop" then cycles through this "classList" and removes the "dropped" class from the given element.
"setTimeout" is used to control when this class removal happens (in the Demo 2000 milliseconds - 2 seconds). Please see below for an additional note.
This function is triggered by the "On Scene Unload" handler in "Scene 1".
Note
In order to hide the switching of colors when the "dropped" class is removed "setTimeout" is used in the function "resetClasses". This is done so the removal of the "dropped" class (i.e. the color change) is delayed by a set amount of time, and therefore not obvious when using Scene transitions other than "Instant".
So for transitions other than "Instant" make sure the "setTimeout" is longer than the Scene transition time You select for the Scene ("Jump to Scene") in the "Actions" menu. In the Demo the Scene transition is 1.1 seconds; in the function the setTimeout is 2000 milliseconds (2 seconds).
You must use milliseconds in the Javascript.
Please see the bottom lines of the code below showing this time set-up.
function "resetClasses"
setTimeout(function(){ // wait 2 seconds (i.e. 2000 milliseconds) before resetting the class(es)
var resetClass = document.querySelectorAll(".dropped");
var i;
for (i = 0; i < resetClass.length; i++) {
resetClass[i].classList.remove("dropped");
}
}, 2000);
// make sure this time is longer than the scene transition time for transitions other than instant. This time is in milliseconds - so our time here, 2000, is equal to 2 seconds
Outstanding! Huge, huge thanks for that - and for the wonderfully informative overview and comments (I love the tip about ‘hiding’ the class change by time-delaying the reset… brilliant!).
It does exactly what I was hoping to achieve… and now I’m going back over it all and studying it with forensic curiosity, just for fun, at 2.00am on a Bank Holiday Monday; yes, I am that sad
The function “resetClasses” is triggered by the “On Scene Unload” event in the Demo.
I found that if I did not use the “setTimeout” method the removeClass (i.e. reset the element colors) would occur before “Scene One” had transitioned to “Scene Two” - or am I not catching your drift?
Screen Capture Example:
“Scene One” to “Scene Two” transition without the “setTimeout” method being used (reset of colors visible):
Actually, I tried this approach first - but realized as a larger strategy - if there were several scenes that were linked to from the "initiating" scene, each "linked to scene" would need to have this code; and it would be more efficient to have a singular "reset" from the initiating Scene.
Also, I had never worked with a "visual reset" before when transitioning Scenes (as opposed to storing data) - I would have thought that "On Scene Unload" cleaned up the visuals after the Scene had transitioned. I wish it worked in this fashion - I do not see the benefit of making any changes (visual resets) manifested immediately - but a minor detail easily compensated.
Beautiful... minimal.
Thanks to You both for your amazing stewardship on this Forum!
In this Demo we are changing the class (i.e. background color established in the "Head HTML" section) of a rectangle element in a persistent symbol from red to blue (and back again) via the "changeRectColor" function triggered by the "Toggle" button in either of the two scenes.
As You will see, going back and forth between scenes yields the same background color for the rectangle unless the color is changed by the "Toggle" button in either scene.
I am sorry but my current project is not going to allow time for working out a solution in the near future - hopefully one of the other Forum members can help out with your request. Good luck!
along these line! Two people same thought…
) extra question… is there a relatively simple way to target the classes that have changed and return them to their original class when a scene reloads?
unless there are other dependencies? That way no need to worry about timeout
