Timeline for Using dom elements for game interaction - slow performance
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2019 at 14:52 | comment | added | Bálint | If those two force the page to be completely redrawn, then it's understandable that it's slow. There's an option to see every redraw happening. | |
| May 23, 2019 at 14:38 | comment | added | vassildador | As Philipp says, the rendering logic for DOM elements is quite complex and dependent on your HTML/CSS. Depending on the CSS properties you use you could end up recalculating the layout and repainting the entire page once for every element you're moving. Without sharing HTML/CSS/JS snippets it's very hard to diagnose this. | |
| May 23, 2019 at 14:17 | comment | added | Philipp | Have you done some profiling with the debugging tools of your web browser to figure out where exactly it spends most of its runtime? And can you add more details about what CSS features exactly you are using for styling and how you are using them? | |
| May 23, 2019 at 14:14 | history | edited | Philipp |
This appears to be a purely technical issue unrelated to the design of your game mechanics.
|
|
| May 21, 2019 at 16:34 | history | asked | user3871 | CC BY-SA 4.0 |