Free for all: BVT control panel
-
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!
-
Thx all, replaced the zip file with new version of the TouchDown webapp so that should now work out of the box.
-
I had the same problem, downloaded 4.0.0 and copied it over the existing files and it worked!
Worked for me too.
On a related note, I have Norton and it kept blocking TouchDown from starting so I had to make an exception for that file. Working like a charm…thanks focal.
-
Do you know if it possible to stop the Safari bounce effect? (i think it is this: http://stackoverflow.com/questions/7768269/ipad-safari-disable-scrolling-and-bounce-effect)
Then you really feel like a native app on the iPad.
-
Do you know if it possible to stop the Safari bounce effect? (i think it is this: http://stackoverflow.com/questions/7768269/ipad-safari-disable-scrolling-and-bounce-effect)
Then you really feel like a native app on the iPad.
Need to test that one, haven’t tried it to be honest. Will get back on this.
-
Here is an example of a website that doesn’t scroll on the iPad: http://www.hakoniemi.net/labs/nonbounce/
-
Need to test that one, haven’t tried it to be honest. Will get back on this.
@Guys,
that link only states that the default behavior does not apply to registered touch events on the Ipad in this case. So, with event prevent default() yes, you’d stop the bouncing effect, but at the same time you’d have to reprogram/reassign the wanted behavior to the registered touch events yourself.
@Focaldesign,
I pm-ed you a usable piece of js-code a while back, which also applies to this situation (Bouncing). Also, in earlier posts in this thread I suggested a feasible way of overcoming issues like thick fingers, longer ‘buttonpresses’ (read: longer touchevent-handling) etc.
Perhaps you’ll find more answers in that approach.Regards,
Fan -
Hi FanOfBMS432,
Received your mail, thx, but I really don’t have the time right now to try that stuff.
it’s plain html/css/js so anyone feel free to mess around in it. All contributions are welcome -
Okay, maybe i have this evening some time and try some stuff. Thanks!
-
Hi FanOfBMS432,
Received your mail, thx, but I really don’t have the time right now to try that stuff.
it’s plain html/css/js so anyone feel free to mess around in it. All contributions are welcomesure, no prob m8. Thanks for the heads-up
I’ll see if I can dig it up and post it here.
Regards,
Fan -
ok, here it is…
The below sees to the js.code which is used by Focaldesign (credits to him for a great piece of work + initiative!!), and gives an idea how to proceed developing the code. One way is to attach events, identified with GetElementsByID.
The touchstart event coupled directly with GetElementByID(‘description here’).onTouchStart() can be used.
An example of code which recognizes a continuous duration of touching the surface.
$(‘#element’).each(function() {
var timeout,
longtouch;$(this).bind(‘touchstart’, function() {
timeout = setTimeout(function() {
longtouch = true;
}, 1000);
}).bind(‘touchend’, function() {
if (longtouch) {
}
longtouch = false;
clearTimeout(timeout);
});});
… Regards,
Fan