Free for all: BVT control panel
-
Making the Buttons Move is not a big deal.
Recieving the current State of the Button from the Game would be interesting. -
i wonder if anybody experienced the same problem.
The App itself works pretty well, there was just one flaw which causes trouble for me.
The reaction time.Every time i pressed a button it takes nearly 1 second before it was recognized by the game.
I have done a little research and it was because of the image map href stuff.
This is handled like a click event but the click event causes the delay.I refactored the default page to use the touchstart event.
Now it works like a charm, the button press is instantly recognized by the game.Anybody else has similar issues?
That’s a great improvement. Care to send me your altered html? Then I can update the version I have shared in the first post here.
Focaldesign,
Many thanks for this. Got this setup on my Nexus 10 tonight and it’s working great. Took me a little bit to get the key commands changed, as they weren’t displaying in the program correctly (despite being saved properly in the HTM file), but things eventually started working. Now it’ll just take me a little bit to get used to actually using my N10, rather than the mouse.
I was wondering if you ever had time to make it so the switches moved visually in the program. Guessing not, but it doesn’t hurt to ask. Thanks again.
Unfortunately I didn’t update it anymore when I started using nomex gloves. The gloves give me a better grip on the Cougar, but my iPad doesn’t recognize my touch anymore ofcourse.
Making them change would be possible, but as rampage says, it would only be interesting when the current state of it can get received from the game. There my knowledge stops -
I will send you the html, share it to the community (currently im at work will do it this evening).
But i have to tell you that my current version is a ICP only view.
Since i “only” have an IPad Mini the Buttons where too small for me so i reduced it to the most important part (at least for me) of your template.If i find some spare time i can do it for your original template too.
-
I will send you the html, share it to the community (currently im at work will do it this evening).
But i have to tell you that my current version is a ICP only view.
Since i “only” have an IPad Mini the Buttons where too small for me so i reduced it to the most important part (at least for me) of your template.If i find some spare time i can do it for your original template too.
Thx, no problem if it’s ICP only. I assume it just requires some find/replace stuff in the html-file, no?
Maybe we can combine yours with mine. In one zip file we can add both the larger image for iPads & other larger tablets, and an ICP only file for iPad mini, smaller tablets and phones? -
A new release has been placed in the first post. A big thanks to Roger Stich aka Rampage for significantly reducing the lag after touch by showing me how to use the onTouchStart()-event instead of links behind image maps.
DOWNLOAD link: http://bit.ly/BVTcontrolpanel20131015
Rampage has a ICP only version optimized for the iPad mini. When I get some free time available, I’ll add it to the package together with an iPhone version.
I’m also thinking about optimizing the javascript & css file with the macro’s in several ways but my technical skills are rusty and I seriously lack spare time for this.
a) using an array for callback (ID) and macro instead of multiple copy/paste lines of javascript ontouch-event;
b) using LESS, compass, SASS for easier css management. I had to change the top offset on all area’s for example. Would have been a lot easier with adjusting a variable instead of all the different items.
c) changing the ID’s in the html to the BMS sim callbacks; and then creating a small php script so one can upload his personal key-file and generate the javascript file for this webapp with his own macro’s already in place. -
wow this is great… I hope I will have time to test it as this lag drove me to stop using it.
-
wow this is great… I hope I will have time to test it as this lag drove me to stop using it.
The difference is incredible. It feels like a native app now on my iPad.
I stopped using it because with the nomex gloves it doesn’t recognize my touch. But I’m thinking (if I ever find the time) to make the several panels from the pit so I can use it for the ramp start. -
A new release has been placed in the first post. A big thanks to Roger Stich aka Rampage for significantly reducing the lag after touch by showing me how to use the onTouchStart()-event instead of links behind image maps.
DOWNLOAD link: http://bit.ly/BVTcontrolpanel20131015
Rampage has a ICP only version optimized for the iPad mini. When I get some free time available, I’ll add it to the package together with an iPhone version.
I’m also thinking about optimizing the javascript & css file with the macro’s in several ways but my technical skills are rusty and I seriously lack spare time for this.
a) using an array for callback (ID) and macro instead of multiple copy/paste lines of javascript ontouch-event;
b) using LESS, compass, SASS for easier css management. I had to change the top offset on all area’s for example. Would have been a lot easier with adjusting a variable instead of all the different items.
c) changing the ID’s in the html to the BMS sim callbacks; and then creating a small php script so one can upload his personal key-file and generate the javascript file for this webapp with his own macro’s already in place.Hi m8,
just reading the topic: If you’d want to get rid of the 300ms ‘default’ lag of the Ipad (& mini + Iphone) using javascript, I can easily help you do that. OnTouchStart event has this 300ms lag by default, you’d have to ‘rip it out’ so to speak.
Also in preventing the screen from scrolling on areas you don’t want it to, etc.Just let me know.
Regards,
Fan -
Hi m8,
just reading the topic: If you’d want to get rid of the 300ms ‘default’ lag of the Ipad (& mini + Iphone) using javascript, I can easily help you do that. OnTouchStart event has this 300ms lag by default, you’d have to ‘rip it out’ so to speak.
Also in preventing the screen from scrolling on areas you don’t want it to, etc.Just let me know.
Regards,
FanHi Fan,
With the ontouchStart I don’t notice a lag anymore. Or maybe I’m getting old and 300ms is unnoticable by me
Yes, preventing scrolling would be nice. The image fits the viewport but iOS has that crappy default thing where you can scroll anyway and it bounces back. If you could tell me how to prevent that, that would be great.
Another small thing I noticed, didn’t research (read: google) yet if or how it can be prevented… When I need a longer touch (e.g. eject, emergency jettison) the iPad recognizes it as a long touch of course and selects the image so you can copy/paste it. -
With the ontouchStart I don’t notice a lag anymore. Or maybe I’m getting old and 300ms is unnoticable by me
It’s there, trust me
Yes, preventing scrolling would be nice. The image fits the viewport but iOS has that crappy default thing where you can scroll anyway and it bounces back. If you could tell me how to prevent that, that would be great.
Sure, no problem. Perhaps we need to setup some ‘live’ moments to go through some stuff? pm me with options if you wish. I could copy code here of course, but that would defeat the purpose of this forum
Another small thing I noticed, didn’t research (read: google) yet if or how it can be prevented… When I need a longer touch (e.g. eject, emergency jettison) the iPad recognizes it as a long touch of course and selects the image so you can copy/paste it.
That’s solvable too. Basic point is here to ‘reassign’ the registered touch events as mouse-events, and then attach behavior to it.
-
I have to correct you a little bit. The 300 ms delay are for click events, thats the reason for onTouchStart, which has in fact no delay as you can read in detail here:
https://developers.google.com/mobile/articles/fast_buttonsDo you have another sources about the delay?
-
I have to correct you a little bit. The 300 ms delay are for click events, thats the reason for onTouchStart, which has in fact no delay as you can read in detail here:
https://developers.google.com/mobile/articles/fast_buttonsDo you have another sources about the delay?
Hmmm…
Pure mathematically speaking you are correct: the touchstart event is seen immediately. However, you only can make use of it when assigned to a function of course. Here’s where the 300ms issue is.
Out of your text: " The problem with this approach is that mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap."
The touchstart is nothing more than an event listener on the touch screen surface. The above is ‘imprinted’ in the default software behavior of the Ipad. So, if you don’t adjust it, it just will be there, for the reason you see above. Sometimes however, you as a designer would want an immediate response, and as you exactly ( ) know what you are doing, you designed your application in such a way that a double tab won’t be needed.
When you say: “click events” they don’t occur. Only 3 events: OnTouchStart, OnTouchMove, OnTouchEnd.
There is however the possibility to use ‘event prevent default’ and reprogramm the event handlers, and simulating recorded touchevents as mouse-events.
In THAT case, we can get rid of the 300ms delay, and do all other kind of stuff (e.g. enlarge the touch-area for people with BIG fingers )Hope that helps,
btw: ‘other sources’: my own programming experience; I use the above in my own software.
Regards,
Fan -
I can’t make it work… I can’t locate the changes I made to make it work… is there a way to import the old files?
I was expecting those files would be the same but needs to redo the same thing as the first time… and I’m totally lost.Edit: never mind I got it. I was on the wrong file… Got it working just fine now.
-
Hi Focal,
I’m trying to use your app but is not working for me. All the connections are fine, I can see the panel on my ipad full screen. I followed your instructions, I changed the key commands to match the ones in my .key file, I was using your previous version of the app with no problems what so ever.
With the previous version, I could see the macros recognized on TouchDown everytime I sent a command from the ipad, but I don’t see them with this new version (is this the way is supposed to be?).
Thanks,
-
No that’s not the way it’s supposed to be
The version for download works with me, so no idea what is wrong. Did you triple check your macro changes in the js-file were correct and you didn’t delete too much or too little (forget a ’ or a ); for example.
Also, did you delete the app from your iPad before installing the new one? Maybe it’s cache. Delete the webapp from your springboard, delete safari cache & temporary files. The start up the server on your pc and surf to the IP address, and then add it again to your homescren/springboard. -
No luck.
I tried your version straight without any edits to the .js file and nothing.
The app connects, I see the panel on the ipad but anything I press does not transmit to TouchDown…I will go back to use the previous version and just live with the delay.
Thanks for the help anyways Focal
-
that’s really strange, I have no idea what could be causing this.
-
No luck.
I tried your version straight without any edits to the .js file and nothing.
The app connects, I see the panel on the ipad but anything I press does not transmit to TouchDown…I will go back to use the previous version and just leave with the delay.
Thanks for the help anyways Focal
HammerRoll - Did you get this figured out? I just tried installing BVT Control Panel and am having similar problems. I have an IPad 2 - I see the panel, but nothing seems to be transmitting to TouchDown.
-
Just found the solution. I updated the TouchDown Web Server software to version 0.3.6.0 (using the “Update Check”) button to get to the support forum. Now everything seems to be working fine. Hope this helps anyone else that may have a similar problem…
-
Just found the solution. I updated the TouchDown Web Server software to version 0.3.6.0 (using the “Update Check”) button to get to the support forum. Now everything seems to be working fine. Hope this helps anyone else that may have a similar problem…
I had the same problem, downloaded 4.0.0 and copied it over the existing files and it worked!