WackyToaster's Profile

- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 10 Aug, 2020
- Quote
I vaguely remember this happening when trying something out with nw.js exports. As you said, it leaves processes running in the background that then prevent the game launching. So in theory, it should always work the first time after restarting the pc. Since I never used the greenworks plugin I doubt that it causes the issue.

I found this 3 year old (and fixed) issue, it seems that may have creeped back in github.com/nwjs/nw.js/issues/6059

And a newer one (I think there are actually several)

github.com/nwjs/nw.js/issues/7122
You could try the solutions from there.
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 2
- 9 Aug, 2020
- Quote
All layouts have a global layer on top that I fade in before the layout changes and on the next layout I fade it out again. There is an animated Sprite on it that is timed so there is no visible cut when the layout changes, apart from a very brief stutter the moment the layout is loaded.
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 2
- 3 Aug, 2020
- Quote
You need to adjust the image points on all the sprite images so they are consistent and it should work how you made it.

I would have the player and the grabber separated. The grabber could be a 9patch object so you can just change the height smoothly to make it expand up.
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 27 Jul, 2020
- Quote
Sounds more or less like a classic Null-Object. I´d take that.
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 26 Jul, 2020
- Quote
Check the layer properties, the layer may have a background set.
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 25 Jul, 2020
- Quote
Short answer: yes, events are executed top to bottom.
You do not have permission to view this post
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 14 Jul, 2020
- Quote
Hell yeah!
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 3
- 12 Jul, 2020
- Quote
A tutorial on how to stop slacking off. :V
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 2
- 7 Jul, 2020
- Quote
You probably need to pick the spritefont object. You say you choose the spritefont that fits the condition, however, I do not see any choosing happening in the events. How exactly are you choosing it?

Right now all spritefont objects in the layout will be picked, that is why you always end up with the start game (simply because it comes first in line) Basically you have to know what spritefont object is currently selected and pick it inside the "on z pressed" event.
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 1 Jul, 2020
- Quote
Set animation frame to Self.AnimationFrame = 0 ? 1 : 0

I think dops method also works. It resolves to 1 if the frame is 0 and vice versa
- WackyToaster
- - Joined 18 Feb, 2014
  - 50 topics • 1,534 posts
- 1
- 28 Jun, 2020
- Quote
Each vertical row is basically a page by doing so. Correct? This would also mean I could use the array.X as the variable to set the page navigation right?

Exactly :)

What I don't fully understand is why you subtract 1 from the 0-based X? Set at XY. X = array.width-1?

When X is set to 0, it basically means the width of the array is 0, as in 0 fields. As it shows in your screenshot, Elements: 0. The moment you push your first note, your array becomes width 1. So right after when you want to set the type/content, you need to access the 0th field and you need to subtract 1 from width to get the last field that was added.

In other words, an array with a width of 3 has three elements that you can access with X=0, X=1, X=2. An array with width 1 has one element that is X=0. And an array with width 0 has no elements to access.