Such a shame, that my one click on 'check solution' (with just one error) is counted twice. Apparently iPads do that...
Posted 3rd Sep 2020 at 15:08 Last edited by gareth 3rd Sep 2020 at 15:11
gareth Administrator Daily subscriber Has not played this puzzle yet
Hi Maartje, I've updated your record so you now show in the first column, and as having just a single check-while-wrong.
There are definitely issues on the iPad where screen presses are counted multiple times in the undo history (I'm not sure why), but I haven't had this happen with the 'Check' button. If it happens again, please do let me know, since that's something I should work around.
Hi Gareth, I am pretty sure this always happens if I press 'check solution' and the puzzle isn't faultless. I would guess I have no puzzles where I have an odd number of 'checked solution while wrong' instances (I always use the iPad). My iPad is very old, that might have something to do with it.
Maartje
Posted 3rd Sep 2020 at 19:38
gareth Administrator Daily subscriber Has not played this puzzle yet
Hi Maartje, That's really interesting (and I'm sorry about that!). I just tested on my iPad Pro and this didn't happen - I got one digit wrong and pressed check, then submitted correctly, and it showed as expected.
I took a look and you have 165 play records with an even number of 'check while wrong' and 125 with an odd number, excluding those with 0 checks while wrong. Of the odd ones, 63 have exactly 1 'check while wrong'.
When you press the button, does it come up with the pop-up saying you are incorrect twice? If not, it really should not double the count. If it comes up twice, then it's definitely the browser sending the button submission twice I think. It's possible there are multiple events being handled for the same process, but if so then I don't know why it wouldn't be absolutely consistent - i.e. all even as you say.
The event is being sent twice, I get the pop up twice. But I tap the button only once (or, at least, that's my intention)
Posted 4th Sep 2020 at 21:23 Last edited by gareth 4th Sep 2020 at 21:25
gareth Administrator Daily subscriber Has not played this puzzle yet
Hi Maartjie, That's really interesting. I would wonder if one of the event handlers for the player is doing something that the iOS Safari objects to, which might mean it didn't think it had handled the button press already, but then that would happen consistently for you. You definitely haven't played other than on iPad? There shouldn't be any way for it to trigger twice as far as the puzzlemix code is concerned - it is just a regular HTML button that calls a function when pressed directly from the HTML element, so the only way that could trigger twice is if the browser genuinely handles the button press twice. Maybe it counts hovering over the screen as multiple rapid presses, but in the case of the 'Check' button the dialog that appears is modal - meaning that it shouldn't receive or store any other events from the page, no matter what, until you dismiss the dialog. I think Safari may be misbehaving, therefore, but it's still my job to work out how and allow for that - there is already plenty of code to specifically handle the iOS browser versions (with varying degrees of success!). Next time I update the player, I'll take a look at this and see if I can reproduce the problem and get to the bottom of it.
Can you open Settings on your device and navigate to General -> About, and let me know the Software Version (i.e. iOS version) and the Model Name (i.e. what iPad you have). I have quite a wide range of iOS devices for testing, so I may have something suitable to reproduce this. And I do apologise for the inconvenience.
Gareth
Posted 5th Sep 2020 at 08:38
HollyBlue Daily subscriber Has started but not yet finished this puzzle
I've noticed the same thing, both the duplicate pop-ups and the multiple taps to undo. Also with the reset pop up. I assumed it was caused by my old iPad. It's third generation, iOS 9.3.5. Usually use my iPad but sometimes laptop. (and rarely phone - too easy to tap the wrong thing!)
It may not be related, but I've also had a problem with Hanjies. If I tap near the edge of the puzzle it sometimes changes the last square I shaded/unshaded to the opposite. I think it's possibly if I accidentaly tap the border of the puzzle that it happens and it occurs more often with the larger puzzle/smaller cell size. Not too much of a problem if I spot it, but if I only realise when I use undo to find where I've gone wrong then it obviously adds to the time. Especially with those extra undo taps! There have been times when I've given up in frustration and it's why I usually do Hanjies larger than 20x20 on the laptop.
Helen (aka Holly)
Posted 5th Sep 2020 at 23:52 Last edited by gareth 5th Sep 2020 at 23:55
gareth Administrator Daily subscriber Has not played this puzzle yet
Hi Helen/Holly, Thanks for letting me know about that. I rarely try Hanjie on my iPad, so I'll give them a go and see if I can create the same issue. It sounds like there is an issue with handling the touch events. The player was never originally designed to work with them because they didn't exist back in 2005 when the player was first written, and there was no HTML support for touch events then anyway, so I think I wrote the touch code by mapping touch events to mouse events in some way. So the mobile/tablet adaptations of the player do need some work, I think.
That's also interesting about the double presses on the buttons - I'll see what versions of iOS I have on some older iPads here.
Sorry: You must log in (create a free user) in order to be able to post comments on this puzzle.
You can however view other players' statistics and comments in the tables above.
Post comment
Key
A yellow/light blue highlight in the time distribution charts highlights your time, where relevant.
Rating scores out of 10.0 show the average difficulty rating chosen by users, where 1.0 is "Easy" and 10.0 is "Hard".
If a puzzle is opened more than once, including by loading from a saved position, then this is potentially a significant aid so it is listed as being completed with 'multiple sessions' for the purpose of the best time/average rating displays above.
Minor aid is defined as no more than one use of 'Check solution' when incomplete and/or no more than one use of 'Check solution' when wrong; and/or using highlighting aids (show repeated digits, show broken inequalities and show valid/invalid placements [slitherlink] only). Major aid is any and all other use of the solving aids except for 'show wrong'.
Last edited by gareth 3rd Sep 2020 at 15:11
I've updated your record so you now show in the first column, and as having just a single check-while-wrong.
There are definitely issues on the iPad where screen presses are counted multiple times in the undo history (I'm not sure why), but I haven't had this happen with the 'Check' button. If it happens again, please do let me know, since that's something I should work around.
I am pretty sure this always happens if I press 'check solution' and the puzzle isn't faultless. I would guess I have no puzzles where I have an odd number of 'checked solution while wrong' instances (I always use the iPad).
My iPad is very old, that might have something to do with it.
Maartje
That's really interesting (and I'm sorry about that!). I just tested on my iPad Pro and this didn't happen - I got one digit wrong and pressed check, then submitted correctly, and it showed as expected.
I took a look and you have 165 play records with an even number of 'check while wrong' and 125 with an odd number, excluding those with 0 checks while wrong. Of the odd ones, 63 have exactly 1 'check while wrong'.
When you press the button, does it come up with the pop-up saying you are incorrect twice? If not, it really should not double the count. If it comes up twice, then it's definitely the browser sending the button submission twice I think. It's possible there are multiple events being handled for the same process, but if so then I don't know why it wouldn't be absolutely consistent - i.e. all even as you say.
Gareth
Last edited by gareth 4th Sep 2020 at 21:25
That's really interesting. I would wonder if one of the event handlers for the player is doing something that the iOS Safari objects to, which might mean it didn't think it had handled the button press already, but then that would happen consistently for you. You definitely haven't played other than on iPad? There shouldn't be any way for it to trigger twice as far as the puzzlemix code is concerned - it is just a regular HTML button that calls a function when pressed directly from the HTML element, so the only way that could trigger twice is if the browser genuinely handles the button press twice. Maybe it counts hovering over the screen as multiple rapid presses, but in the case of the 'Check' button the dialog that appears is modal - meaning that it shouldn't receive or store any other events from the page, no matter what, until you dismiss the dialog. I think Safari may be misbehaving, therefore, but it's still my job to work out how and allow for that - there is already plenty of code to specifically handle the iOS browser versions (with varying degrees of success!). Next time I update the player, I'll take a look at this and see if I can reproduce the problem and get to the bottom of it.
Can you open Settings on your device and navigate to General -> About, and let me know the Software Version (i.e. iOS version) and the Model Name (i.e. what iPad you have). I have quite a wide range of iOS devices for testing, so I may have something suitable to reproduce this. And I do apologise for the inconvenience.
Gareth
It may not be related, but I've also had a problem with Hanjies. If I tap near the edge of the puzzle it sometimes changes the last square I shaded/unshaded to the opposite. I think it's possibly if I accidentaly tap the border of the puzzle that it happens and it occurs more often with the larger puzzle/smaller cell size. Not too much of a problem if I spot it, but if I only realise when I use undo to find where I've gone wrong then it obviously adds to the time. Especially with those extra undo taps! There have been times when I've given up in frustration and it's why I usually do Hanjies larger than 20x20 on the laptop.
Helen (aka Holly)
Last edited by gareth 5th Sep 2020 at 23:55
Thanks for letting me know about that. I rarely try Hanjie on my iPad, so I'll give them a go and see if I can create the same issue. It sounds like there is an issue with handling the touch events. The player was never originally designed to work with them because they didn't exist back in 2005 when the player was first written, and there was no HTML support for touch events then anyway, so I think I wrote the touch code by mapping touch events to mouse events in some way. So the mobile/tablet adaptations of the player do need some work, I think.
That's also interesting about the double presses on the buttons - I'll see what versions of iOS I have on some older iPads here.
Gareth
You can however view other players' statistics and comments in the tables above.