-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Button click with Ipad Pro not always responding #1
Comments
Hi Magicnorm, I'll investigate this issue further. Another user with an ipad pro is also experiencing the issue. |
FYI, I tried with a friends regular Ipad and I did not have any problems. |
Are you using Safari on the iPad pro? Would you mind testing with another browser like Chrome or Firefox, just to help me pin down if the issue is browser related or not? Unfortunately I don't own an iPad Pro (only a regular iPad), so I need to rely on feedback to troubleshoot the issue. |
Sorry, I should of mention it, I did test with Chrome on Ipad Pro and I had the same problem.. |
Ok. I removed the sound thing for the moment (I suspect it might be related to the problem), along with some other tweaks on the client side. I've zipped the client files again for you to test. http://fcdu.fergonez.net/tests/WebClient.zip If you don't mind please follow these steps to guarantee that all the files will be replaced:
KR, |
magicnorm, I think I managed to reproduce the issue you are having. As I said, I don't have an iPad Pro, but I have the 2019 7th generation version with iPadOS 15.5 and I managed to experience something similar about it not registering the clicks. Can you please enable the "Verbose log" on the server, and check if it is at least receiving the clicks from the client? It should display messages like A regular session log, when you click the buttons on the client, should look something like this: |
To clarify, do you want me to do the test with the old or the new version? |
With the new version: 1.0.8230 |
I did not see any keys reported in the log. After refreshing my browser I saw this: log: |
Did you still experience the issue with the client stop responding? By looking at the log, it seems that it's registering the clicks and responding accordingly:
In this example, you pressed RSK5 (first line), the sim updated the screen (second line) and the server sent the updated screen to the client (third line) |
It stop responding at [12:37:26], I did a refresh at [12:43:05], and it was OK after. Between that no keys were registered. |
Ok, I see. As you mentioned that you could still hear the first click sound, I'm guessing the browser is still using the page from the Chrome/Safari cache instead of requesting a new one from the server. If you don't mind, I'm preparing a whole new release with quite a few changes in the communication and I hope they will solve the issue (including the audio lag, the cache, etc). I think I can send you a preliminar version of it by the end of the day. |
Great |
Hey magicnorm, Here's a preview of the next release, with quite a few bug fixes. The click audio in this one is also disabled by default (if you still hear it on the client, make sure to clean the browser's cache) Please let me know how it goes. |
Fergo, there is still a problem. When I type, sometime, I do not see the log registering the keys. After a few seconds I see the keys registering in the log. Like you said in a earlier post it looks like it's lagging. At other times nothing. I refresh the browser and I have control again. One thing I noticed is that it often the problem starts when I hit the PREV PAGE or the EXEC button. I don't know if this helps. Since I cleared the cache I do not ear button click anymore. But I would like to see this work, at least you know you've click the button. ;) Also, I tested with a Ipad (Not a Pro) and everything was OK. OK |
Hey magicnorm, Another user with an iPad Pro mentioned that it registers fine when using an Apple Pen, but not with your fingers, so I think these iPad treat touch gestures differently than other devices. I intend to push another update tomorrow with changes on how the button presses are detected, hoping it will fix the issue. |
Hi Fergo, |
He'll be out of town until mid-week. You can do this in the following menu: Settings -> Safari -> Advanced (last item) -> Website Data -> Search for the IP address and swipe left on it to clear the cache |
I did do it before testing. |
When I get back home I'll take another look into it. |
What version of iPad OS are you running on your iPad Pro? |
The latest 15.6 |
Managed to borrow an iPad Pro 11" on 15.6 from a friend. Confirmed the issue with the buttons not responding properly, specially Prev/Next page. I rewrote quite a lot of the code and now it's working fine on the iPad Pro and all other previous devices that I had already tested on. I've pushed it to flightsim.to, but you can download it here too: https://fcdu.fergonez.net/tests/fcdu_20220728_114805.zip Please do a fresh install (delete the old version and extract this new one) |
Did a fast check and everything seams to be working great. Will test more tomorrow. Thank You. |
I left it temporarily disabled for the moment so I could better tackle one issue at the time. You can still enable it by editing the file After I confirm the button issue is definitely fixed, I'll get back into these other bugs. |
FYI |
Great! Thank you very much. |
I am using Safari on a Ipad Pro and often when I click on buttons the application does not respond to keys and I need to do a refresh.
Also the button click sound often disappears.
The text was updated successfully, but these errors were encountered: