Free for all: BVT control panel
-
now guys any good way (mozila maybe???) to spot coordinates so what i want to do is put the whole cockpit there. I dont mind scrolling also i have 3 tablets… the problem is that the server accepts only from one device, the good thing is that u can run the server more then once!!! so it should work… right?
-
Nah doesn’t work
It does look like the combination CTRL and {e down} doesn’t.
javascript:macro(“^{e down}”);pause(10000);macro(“{e up}”); or javascript:macro(“^{e down}”)
When you use e down, the CTRL isn’t recognised and will give as result the element commands.
Headache and sleepless nights, it cannot be that difficult
It doesn’t recognize the ctrl hold down I assume. Try with {CTRLDOWN} ->Holds the CTRL key down until {CTRLUP} is sent.
now guys any good way (mozila maybe???) to spot coordinates so what i want to do is put the whole cockpit there. I dont mind scrolling also i have 3 tablets… the problem is that the server accepts only from one device, the good thing is that u can run the server more then once!!! so it should work… right?
Upload image at http://www.image-maps.com/ and drag & drop the clickable area’s and then let it generate the coordinates html lines (areas).
For the 3 devices, you could make html files for each device, and change the index.html to a page with 3 links, you open index.html from the server app on each device and then click to the correct page with the clickable image for that device. -
{Ctrldown} doesn’t work either in combination.
Look like mission impossible.
-
Got it……
After each command there should be pause else it will not be recognized.
Final line is:
href=‘javascript:macro (“q9”); pause(1000); macro(“{CTRLDOWN}”);pause(2600);macro(“{e down}”);pause(3000);macro(“{CTRLUP}”);pause(1600);macro(“{e up}”);’ alt=“EJECT” title=“EJECT” />
This will call resue choppers (=q9) and then eject from pit.
-
Upload image at http://www.image-maps.com/ and drag & drop the clickable area’s and then let it generate the coordinates html lines (areas).
For the 3 devices, you could make html files for each device, and change the index.html to a page with 3 links, you open index.html from the server app on each device and then click to the correct page with the clickable image for that device.U mean I can use only one server?
As I see it is 3 different files with 3 instances of server running on the pc… cause I have to declare the allowed device IP. -
Haven’t tried that yet. Don’t know if that’ll work.
-
Just got this setup on my ipad and works really well. Many thanks for posting I have been looking for a way use the icp on this device for ages. I tried the one where you have to pay for the app and I just couldn’t get that to run consistently well.
Cheers!!
-
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?
-
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.
-
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?