Okay - could you please ask the teacher to go to
And send us a picture of the results. They look something like this:
It would be interesting to see on a working board and a non-working board.
Hello. I think the problem here is related to the touch logic of the ViewSonic interactive whiteboard. Because the zim code works flawlessly in current Chrome browsers.
However, the create.js touch code doesn't support listeners like pointerdown and pointermove. When I asked the AI about this problem, it wrote that such problems occur with ViewSonic whiteboards.
My idea is to make create.js touch.js compatible with all inputs and pointerevents. In our code, the ViewSonic whiteboard detects the Chrome browser, but the touch logic is different. I don't fully understand it, but what I'm thinking is: The interactive whiteboard has a Windows system, Chrome browser, but the touch logic is like iOS or Android (of course, this is an analogy; I don't know the technical details). Therefore, the most definitive solution is to convert the touch.js part to pointerevents. I will get suggestions from the AI for this and share them with you.
1 Like
I think this approach makes sense to establish what is going on. I've sent this out to a few schools.
Thank you for all your efforts.
Yes. Ferudun sent us possible fixes - thanks, Ferudun. I think getting the data and trying to fix it with as little change as possible would be best - but will take a look at the AI solution if we are stumped. Chris, let us know when you get an answer back.
1 Like
Chris,
The touch.html test file that I sent you will show us various test values.
@Ferudun did some modifications based on the AI code to prioritize pointers (just swapping our test order) and it tested well (but he did not test on viewsonic). Whit this change, it means that desktop, etc. now use pointer events, which should work, but are different events than we have been using... so there is a risk of some other things not working...
I have made a drag2.html test that uses the new pointer-event-prioritized code and has a basic ZIM drag() on the red circle.
The test still shows the various test values (like the touch page). So this is the preferred test page for the teachers to report on. If we could have them screenshot the values or provide a short vid like last time, and see if the circle drags on their boards.
Thanks.
2 Likes
Thank you for the updated test page. I've sent it out and fingers crossed I get some responses as none came from the last batch I sent out.
Right - I figured the new file would also work as a reminder...
Here is the first result to come back - the circle didn't move!
Board: Promethean 74” Cobalt AP7-A65
Browser: MS Edge (latest)
Okay - that explains it.
We are not even getting past the Touch.isSupported because the onTouchStart and the maxTouchPoints are returning false. I have to teach now - but will work on this later.
1 Like
Here is hopefully, a final test:
We have removed the maxTouchPoints > 0 part as it seems the board is reporting the wrong number. Ferudun concurs. I have contacted their support about it to see what they say. At the AI and Ferudun recommendation, we have also moved the pointer events to above the touch events. We have tested everything that we can think of in ZIM with pointer events and they seem fine. (general mouse events, drag, drag with cursor outside browser, gesture, tap with double click, hov, motionController, TextureActive)
So, could you ask the teacher to let us know if the circle drags and take a screenshot of the page. Thanks.
We have lift off! Dragging is now working on the Promethean board. Thank you so much for your persistence! It would been interesting to see the value of maxTouchPoints that the board was reporting.
I've also successfully tested it on:
- Google Pixel 9a phone (Chrome)
- OnePlus Pad 2 tablet (Chrome)
- iPad + iPhone (Safari + Duck Duck Go)
- Windows 11 touchscreen laptop (Edge, Chrome v139 and v143 + Firefox)
- Chromebook with touchscreen (Chrome)
- Windows 11 + Ubuntu desktops without touchscreens
Hopefully the other schools get back with more positive results!
2 Likes
We will do more testing this afternoon and then patch the createjs and let you know.
Woah this is amazing! Thank you so much everybody for this amazing work. I'm sorry, I've only just seen this. I didn't get any feedback from any of the people I sent the first page to. I'm going to the BETT educational technology show in London next week. I was hoping to try the file and some games on ViewSonic and others there. It has been impossible to speak to Promethean.
1 Like
I'm on https://sett-vlaanderen.be 25 feb 2026 an https://ipon.nl with ZIM Netherlands
taking about you @Jamesbrrtt and ictgames see
1 Like
Wow, that's awesome Karel. Flying the flag for ZIMjs in schools too. Thank you for including ictgames in your presentation! Hope it goes brilliantly!
1 Like
come along to belgium 25 feb.. over the northsea welcome at my house..
1 Like
@Core did you manage to test the new Pointer Events implementation in CreateJS with as many browsers and devices as possible? It's a modernization that will hopefully pay off so please help out.
Please ensure the circle is draggable; if not submit a screenshot and i it works let us know:
I went to try a couple touch screens at Sheridan and they could not get them going so they are trying to fix them. I had a dozen students try their mobiles and they all worked. My touch screen works (HP monitor - Pavilion 23tm) @Ferudun tested on his interactive whiteboard and it worked.
We came in to patch createjs 1.5 which is used by ZIM 019 and just launched fairly recently... call it within the patch time.
The question is... do we retro patch older versions. I guess, patching 1.5 and seeing how it goes for a while, then deciding.
It works on my Wacom Cintiq and iPad. Will try some boards this week.
1 Like
Let me know when the 1.5 patch / ZIM 019 combo is live and I update some of my resources to use it, and give it a test.
1 Like