Obsolete
Status Update
Comments
lo...@gmail.com <lo...@gmail.com> #2
The iPhone Simulator has a nice UI for this. You hold down a key combo and you see
two finger spots on the emulator screen, mirrored around the center of the screen.
Drag away from the center to pinch open; drag toward the center to pinch closed.
two finger spots on the emulator screen, mirrored around the center of the screen.
Drag away from the center to pinch open; drag toward the center to pinch closed.
lo...@gmail.com <lo...@gmail.com> #3
That is nice, but that only handles the case of "pinch". It would be a good start,
and would handle probably the majority of common use cases, but there are certainly
very many ways I can move two fingers at once that don't even resemble a pinch. :)
and would handle probably the majority of common use cases, but there are certainly
very many ways I can move two fingers at once that don't even resemble a pinch. :)
je...@gmail.com <je...@gmail.com> #5
This would be really handy. I would also like to mention that many people with TUIO devices would love to use them to test.
ma...@gmail.com <ma...@gmail.com> #6
Pinch is by far the most common multi-touch gesture IMHO. Also, the iPhone simulator also simulates two-fingered scrolling (dragging across the screen with two fingers). I can't think of any other two-fingered gesture that would make sense in a UI :)
Currently the Android version of our app is on hold because it uses multi-touch and we don't have an actual device to test it on.
Currently the Android version of our app is on hold because it uses multi-touch and we don't have an actual device to test it on.
to...@gmail.com <to...@gmail.com> #7
Rotation is another useful gesture.
Whatever the "common gestures" are, it would be nice to be able to hold down certain keys on the keyboard to perform these gestures in the emulator. E.g. Ctrl for pinch, Alt for Rotate, etc.
In addition, I would like to be able to move additional pointers freely. It could work by holding down number keys, for instance. Holding/pressing "1" would freeze all current pointers and let you control the first pointer with the mouse (up/down/move). Holding/pressing "2" would freeze all current pointers and let you control the second pointer (up/down/move). Etc. This would be useful for apps that use actual multitouch and not just gestures.
Whatever the "common gestures" are, it would be nice to be able to hold down certain keys on the keyboard to perform these gestures in the emulator. E.g. Ctrl for pinch, Alt for Rotate, etc.
In addition, I would like to be able to move additional pointers freely. It could work by holding down number keys, for instance. Holding/pressing "1" would freeze all current pointers and let you control the first pointer with the mouse (up/down/move). Holding/pressing "2" would freeze all current pointers and let you control the second pointer (up/down/move). Etc. This would be useful for apps that use actual multitouch and not just gestures.
pd...@gmail.com <pd...@gmail.com> #8
Ahhh, come on, guys! We need the right tools to help Google make its projected $10 billion/year on Android. Can't you get an intern to do this? Or a new college hire?
[Deleted User] <[Deleted User]> #10
With TUIO support, we could use the TUIO Simulator for testing Multi-Touch. I used that tool to develop a tabletop Application.
But a solution which is integrated into the android simulator would be much more handy.
But a solution which is integrated into the android simulator would be much more handy.
sh...@gmail.com <sh...@gmail.com> #11
MPX input on the emulator is very much needed! So hopefully this will be added soon! Without multi-touch apps, Android will never surpass the iPhone.
When we talk about MPX, we're not just talking about two fingers... I hope Android allows mapping of, say, four fingers simultaneously.
When we talk about MPX, we're not just talking about two fingers... I hope Android allows mapping of, say, four fingers simultaneously.
ew...@gmail.com <ew...@gmail.com> #12
I'm thinking of a way to develop an application that you can run on your android phone, connect the phone via usb and have the emulator redirect the input form the phone to the virtual device. This way you can test multi-touch inside the emulator using a real device. I've no idea of the applicability of this solution, and whether there's something like that already implemented, so comments and guidance would be appreciated :)
sa...@gmail.com <sa...@gmail.com> #13
To #11, that would be a nice idea, but you have to keep in mind there are very different screen sizes and formats and doing letterboxing to, say, map a 16:9 real screen to a 4:3 or 1:1 screen might not be ideal.
Still, it's a nice idea to work around this while the emulator doesn't have direct support, IMHO.
Still, it's a nice idea to work around this while the emulator doesn't have direct support, IMHO.
ga...@gmail.com <ga...@gmail.com> #14
[Comment deleted]
an...@gmail.com <an...@gmail.com> #15
This feature is especially important since multitouch has been enabled since 2.0.
Even considering how bad Eclipse is, the emulator is the worst part of the SDK. It's slow. Try the iOS Simulator is relatively fast and doesn't take a minute to launch.
Even considering how bad Eclipse is, the emulator is the worst part of the SDK. It's slow. Try the iOS Simulator is relatively fast and doesn't take a minute to launch.
ju...@gmail.com <ju...@gmail.com> #16
To be fair, the Android emulator is a legitimate phone emulator. Almost _anything_ you can do with a real phone can be successfully tested in the emulator (save for multitouch, obviously, but that's an interface issue, not a software issue). It really is emulating the ARM processor, which is what makes it slow. The iPhone simulator does not actually emulate anything. The "simulator" label is very appropriate, because it only simulates enough of iOS to run a version of your application (not necessarily the final compiled version that will run on the phone), so you can't really say for sure that "works in the simulator, works on the phone" like you can with Android's emulator. Closer to it's original release, there were even a couple guys who hooked up GPS and an accelerometer to the emulator and used their laptop to test the app they'd developed before we had any physical phones, which is something the iPhone simulator couldn't even dream of.
Not to downplay the need for multitouch, but need to give props to the emulator folks where props are due, because they've done some seriously cool work.
Not to downplay the need for multitouch, but need to give props to the emulator folks where props are due, because they've done some seriously cool work.
ed...@gmail.com <ed...@gmail.com> #17
Any official word from Google on this? Apart from making the SDK faster, this is second on my wish list. It's more than I nice-to-have. You can't seriously test anything multitouch-related without an actual device, which is a pretty big drawback.
Also, to clarify another comment above: you can do more than multitouch scale (pinch-to-zoom) in the iOS simulator. You can also rotate elements. It's not as natural as it would be on an actual device, but it's passable. Right now it's completely impossible in the Android emulator, save for actually simulating the events in JavaScript.
Also, to clarify another comment above: you can do more than multitouch scale (pinch-to-zoom) in the iOS simulator. You can also rotate elements. It's not as natural as it would be on an actual device, but it's passable. Right now it's completely impossible in the Android emulator, save for actually simulating the events in JavaScript.
em...@gmail.com <em...@gmail.com> #18
Google doesn't comment on (or read) bug reports in this issue tracker.
This issue is in the status "New", which means that no Googler has reviewed the issue. Unfortunately, it's not alone; 80% of the top 100 Defects are "New."
http://code.google.com/p/android/issues/list?q=Type%3ADefect&sort=-stars
And it's even worse when you look at the top 100 enhancements, all of which have more stars than this issue.
http://code.google.com/p/android/issues/list?q=Type%3AEnhancement&sort=-stars
This issue is in the status "New", which means that no Googler has reviewed the issue. Unfortunately, it's not alone; 80% of the top 100 Defects are "New."
And it's even worse when you look at the top 100 enhancements, all of which have more stars than this issue.
co...@sincero.cl <co...@sincero.cl> #19
Well, in r17 they've finally added "Multi-Touch" support, as detailed here: http://tools.android.com/tips/hardware-emulation#TOC-Multi-Touch
However, to use this multitouch support requires a phone tethered running their multi-touch simulation software, so it's still limited to folks owning a real phone, in which case you might as well test directly on the phone.
However, to use this multitouch support requires a phone tethered running their multi-touch simulation software, so it's still limited to folks owning a real phone, in which case you might as well test directly on the phone.
um...@gmail.com <um...@gmail.com> #20
Hi there,
the online documentation is not up to date
see
http://code.google.com/p/android/issues/detail?id=34868
use the instruction you find in the SdkController application itself.
the online documentation is not up to date
see
use the instruction you find in the SdkController application itself.
ca...@gmail.com <ca...@gmail.com> #21
I'd like to see this feature implemented not so much because I don't have a device, but because sometimes I would like to:
1) Test multi-touch with different Android versions,
2) Develop on a remote desktop (hence no possibility to attach a physical device).
1) Test multi-touch with different Android versions,
2) Develop on a remote desktop (hence no possibility to attach a physical device).
th...@gmail.com <th...@gmail.com> #22
[Comment deleted]
ma...@gmail.com <ma...@gmail.com> #23
[Comment deleted]
le...@gmail.com <le...@gmail.com> #24
[Comment deleted]
da...@gmail.com <da...@gmail.com> #25
[Comment deleted]
ca...@gmail.com <ca...@gmail.com> #26
Implemented by CL 185430
ma...@gmail.com <ma...@gmail.com> #27
Specifically, a pinch/rotate gesture was added in Emulator release 25.0.4 preview 5 - hold Alt to bring up the interface.
Reference issue 36949180 to track the addition of a "two-finger swipe gesture".
Reference issue 36949180 to track the addition of an interface for general multitouch input.
Reference
Reference
ne...@gmail.com <ne...@gmail.com> #28
Nexus 4 with Android 4.4.2. No way of accessing history altough there is a way of clearing it. Ridiculous!
ma...@gmail.com <ma...@gmail.com> #29
Nexus 5, 4.4.2 same problem,
le...@gmail.com <le...@gmail.com> #30
Nexus 4, 4.4.3. The issue persists.
sa...@gmail.com <sa...@gmail.com> #31
Damn you Google, can't you make that possible already!!
BTW using Nexus 5 4.4.3
BTW using Nexus 5 4.4.3
wa...@gmail.com <wa...@gmail.com> #32
How useless a calculator is without history.
Using Nexus 4 and version 4.4.4. Android guys please fix this
Using Nexus 4 and version 4.4.4. Android guys please fix this
ki...@gmail.com <ki...@gmail.com> #33
MotoX android version. 4.4.2. How ridiculous that this easily rectified problem still persists. Is there actually a history, or is that "clear history" button just for show?
ja...@gmail.com <ja...@gmail.com> #34
Is this issue every going to get fixed? No history access for my N7 or N5... that's just crazy to not have history access on your flagship google devices.
te...@gmail.com <te...@gmail.com> #35
I've seen the history before but its only when I put it in my pocket and hit buttons somehow. I have not been able to find it on my own.
po...@gmail.com <po...@gmail.com> #36
"Clear history" feature looks like a joke. Please, fix this.
em...@esoko.com <em...@esoko.com> #37
[Comment deleted]
je...@googlemail.com <je...@googlemail.com> #38
Please fix very annoying.
yu...@gmail.com <yu...@gmail.com> #39
[Comment deleted]
yu...@gmail.com <yu...@gmail.com> #40
I don’t think Google will fix it in this application. Android 5 calculator doesn't have this stupid “Clean history” option. Everything is very consistent there - no history and no “Clean history”. :) Also Google removed in Android 5 any support for clipboard, no copy, no paste. Be prepared!
So, CyanogenMod Calculator is very good choice.
So, CyanogenMod Calculator is very good choice.
yu...@gmail.com <yu...@gmail.com> #41
I found a funny way to access the history. :) Connect an external Bluetooth keyboard with an Android device. (I have Verbatim). Arrow keys work as a touchpad and you can browse the history by pressing up and down keys. :)
ha...@unlv.nevada.edu <ha...@unlv.nevada.edu> #42
[Comment deleted]
ha...@unlv.nevada.edu <ha...@unlv.nevada.edu> #43
Turn off the calculator app. Go to 'settings', 'application manager', 'calculator', 'clear data'. No more old calculations showing.
lo...@gmail.com <lo...@gmail.com> #44
I can't find history on my Moto G calculator Android
sa...@google.com <sa...@google.com> #45
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
sa...@gmail.com <sa...@gmail.com> #46
How to see calculator history for 2 months back, only see new calculate amt
Description
- Steps to reproduce the problem.
Open the calculator application and do some equations.
- What happened.
There is no way to view the history (although the clear option is available).
- What you think the correct behavior should be.
There should be a way to view the history.