Heya! I'm currently working on a photoshop panel using elm, and am nearing completion. It's working very smoothly on the windows version of photoshop, but i finally went to test it on mac, and found that it was running at exactly 2 fps (multiple versions of photoshop, 2 separate macs).
I' spent all of yesterday to no avail trying to track it down, and got some hints but still am not there yet. First thing i did was run some isolated example code, a webgl cube spinning, and a timer counting up using animationFrame. Both exhibited identical chugging. WIth photoshop i only have limited debug tools, (can't open the elm debug window in photoshop sadly). going into it, it seems that every frame is taking 500ms give or take 5-10ms, as opposed to it taking 16ms per frame in chrome (photoshop runs a version of chromium internally, which i tested on outside of photoshop as well, it runs fine). <https://lh3.googleusercontent.com/-tk4RA9ypeRo/WJJ8FoXMdpI/AAAAAAAABpo/gja3D6G5RBomEu2KCYgJASgr1MF-RSnmACLcB/s1600/Screen%2BShot%2B2017-02-01%2Bat%2B5.55.17%2BPM.png> Inspecting the chugging, i am pretty certain it has to do with timers.js, and timing out. On the timer counting up example, in the output js there was a requestAnimationFrame function that i replaced with a setInterval(1000/60), and it started counting up at 60fps as we would expect, albeit not very smooth. This bug has been destroying me, and it's such a niche test case, being that i am a one man team trying to do this. Any idea for where i can look in the code, or what information you would need to help debug this? Thanks! -Muzz -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
