a goodly portion of learning how to program well is learning how to debug and find out exactly what's going on for yourself. what's your program doing? what is it doing that you don't realise it doing, and where and why is it doing that?
the majority of bugs i have ever repaired, the people i approached didn't know enough about my codebase to be able to solve it -- but they were able to point me in the right direction, or sometimes just telling them fixed it (a la rubber duck programming).
so, consider this a personal development exercise in how to debug things, which is a critical skill to learn.
room topic changed to Game Development: Game development and other polite discussion. Game development conversations have priority. Please star responsibly. Be Nice applies here: gamedev.stackexchange.com/help/be-nice [game-design] [game-industry] [rubber-ducks]
You can see in the picture that I have a Canvas with a popup menu in it. I just enable this, and it covers the main menu stuff. Clicks go through it and hit stuff in the main menu.
I've tried adding an EventTrigger to the PopupRoot object, and adding an event to listen for PointerClick events,...
I think everyone can learn to program, though not necessarily in something arcane like C. I think most people can learn the basics in something like python or BASIC
You can see in the picture that I have a Canvas with a popup menu in it. I just enable this, and it covers the main menu stuff. Clicks go through it and hit stuff in the main menu.
I've tried adding an EventTrigger to the PopupRoot object, and adding an event to listen for PointerClick events,...
