- This topic has 31 replies, 5 voices, and was last updated 10 hours, 52 minutes ago by
.
-
Under console.log, tried to put window.PetraBasicMoveRange under the right side, under JSON3 and under windowprototype, still didn’t work.
Which part of the right side of console log did you put window.PetraBasicMoveRange?
Also tried to write it on the left side, still didn’t work when I went fullscreen
Also, even though this code technically works, the PetraBasicMoveRange var in fullscreen still has the same speed as in small windows.
On the first response:
look up v3d.puzzles.procedures and it will give you a list of all the procedures. You can call one of them by typing v3d.puzzles.procedures.theNameOfTheProcedureYouWantToCall
you don’t want to try setting anything to the window with v3d.puzzles.procedures.window…
To set a window object/key you just set window.PetraBasicMove = 12 since you defined this to the window and use it in your procedure, you can set the move rate
window.PetraBasicMove = 12
and then call the function (procedure) that calls the movement.
v3d.puzzles.procedure.movePetra if your function is not setting the speed it uses then it will change the speed.
It’s really hard without seeing what exactly you are trying to accomplish, but just trying to help you understand the concepts.
You have to re-fire the procedure or it wont change.
here are some screenshots of a simple example to conceptualize it.
Here is another example on how to set the window key petraBasicSpeed value to 12 from the console and then you have two functions that you can call to set it to the defined amount.
Hope this helps
I tried to do the first one, sadly no change in speed during fullscreen
Do i go to console.log when the verge3d is in fullscreen to activate this:
or just normal screen?
tried in visual studio code, in fullscreen function still no change. Any suggestions?
Wait, so you’re telling me that doing it in console log is not to trigger event, but to see if it works, as in no error?
doing it in the console.log is just the easiest way to explain it and you can instantly see what your calling and if it works or not, but what you really want is to use those calls in the code so it can react.
I don’t see why you cant do all of this from the puzzle environment. but its good to get outside of it anyway, for extra learning and incase you need to add more functionality to anything.
I just think it’s better to put fullscreen button outside verge3d, like that of a youtube video’s. As you say, it’s definitely good to learn more coding for more versatility and flexibility to website or app.
You can call any function in the console, so its easier to test that you’re calling it correctly that way rather than putting it in code.
So I should have explained this too, to call the function you have to put the () at the end. It looks like you are just referencing the key values for Petra —not actually calling them, so that wont work.
try this
let elem = document.getElementById(gamescreen);function fullscreen() {
if (elem.requestFullscreen) {
elem.requestFullscreen();
window.PetraBasicSpeed = 0.007;
console.log(‘PetraBasicSpeed set (standard):’, window.PetraBasicSpeed);
} else if (elem.webkitRequestFullscreen) { // Safari
elem.webkitRequestFullscreen();
window.PetraBasicSpeed = 0.12;
console.log(‘PetraBasicSpeed set (webkit):’, window.PetraBasicSpeed);
} else if (elem.msRequestFullscreen) { // IE11
elem.msRequestFullscreen();
window.PetraBasicSpeed = 0.25;
console.log(‘PetraBasicSpeed set (ms):’, window.PetraBasicSpeed);
}
}
and then you have to recall the function that sets the speed. How are you setting the speed? Whats the function look like?
- You must be logged in to reply to this topic.