IssueTracker

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.

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.  :)

It is impossible to test multitouch gestures without having a multitouch capable
device... please add at least comment#1 suggestion !

This would be really handy.  I would also like to mention that many people with TUIO devices would love to use them to test.

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.

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.

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?

I want to second request the MPX support. Also supporting an standard protocol such as TUIO (tuio.org) will be very handy. That would make porting multi-touch apps to android a breeze.

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.

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.

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 :)

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.

[Comment deleted]

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.

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.

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.

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

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.

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.

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).

[Comment deleted]

[Comment deleted]

[Comment deleted]

There is a work around on stackoverflow: https://stackoverflow.com/questions/47479954/how-to-ask-for-user-input-in-on-edit-installable-trigger-in-google-spreadsheet/ . But it's far less good than a simple onEdit-promt or -modalDialog. :-/

@google: a fixture would really be appreciated!

Implemented by CL 185430

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.

I will look at it on monday, but I am almost sure that we have no manifest.

So I will come back after trying this option.




2018-07-13 20:54 GMT+02:00 <buganizer-system@google.com>:

>I will look at it on monday, but I am almost sure that we have no manifest.
>So I will come back after trying this option.

Be careful. You have to add all scopes which you need for your app.
Check some scopes here https://github.com/oshliaer/google-apps-script-snippets/labels/oh-my-scopes

After some tinkering (the manifest file format is not precisely described in the documentation) I got a working manifest :
{
  "timeZone": "Europe/Paris",
  "oauthScopes": [
     "https://www.googleapis.com/auth/script.container.ui",
        "https://www.googleapis.com/auth/documents",
        "https://www.googleapis.com/auth/userinfo.email"
  ],
  "dependencies": {
  },
  "exceptionLogging": "STACKDRIVER"
}
If I authorize the addon via the link I get :
- first : This app isn't verified , which seems normal as my test environment is not verified indeed
- second : validation prompt for these :
View and manage your Google Docs documentsMore info
Display and run third-party web content in prompts and sidebars inside Google applications    --> what is the oauth scope of this one ? I don't know
and then if I reopen the document, making sure that the add-on is supposed to be authorized for the document, the add-on doesn't open
in stackdriver I still get this error :
  "The script does not have permission to get the active user's identity."  

it seems to me this is better than before, but not working

Did I miss some scope I should add to the manifest ? Or is there more to it ?

and ... I still have in stackdriver this message : Error showing sidebar  Exception: You do not have permission to call showSidebar

yv.. do you have any API calls to a third-party on the client side (e.g.
Stripe)?

Steve Webster
*G Suite Sr Solutions Architect and Developer
<https://plus.google.com/u/0/+SteveWebster-gmail/about>  ||  SW gApps
<https://sites.google.com/site/swgapsp/>*
Google Top Contributor in: Google Apps Script, Drive, and Docs
Google Vendor (2012-2013) || Google Apps Developer Blog Guest Blogger
NEW! Google Apps Script Support Plans w/Real-time Monitoring
<http://www.swgapps.com>
G+ Community Owner: Developing add-ons for Google Docs/Sheets/Forms
<https://plus.google.com/u/0/communities/117193953428311185494>
Add-ons: Text gBlaster
<https://chrome.google.com/webstore/detail/text-gblaster-sms-texting/pbbgimdnldlfkdichlcaonmmbfnddibh?utm_source=permalink>
, Remove Blank Rows
<https://chrome.google.com/webstore/detail/remove-blank-rows/gmidogdphchbiehdmbigdbcopkpjpnio?utm_source=permalink>
and
Side Study for Teachers <https://goo.gl/z1jZds>

On Mon, Jul 16, 2018 at 9:56 AM, <buganizer-system@google.com> wrote:

We do not call third party APIs like stripe, but we do load a vue.js application we created to handle the sidebar interaction.
That vue.js application is hosted outside of the appscript project as a static content on one of our server.

yv.., Okay. I was speculating if client side third-party activity could be
a root-cause. Any thoughts on this idea, Google Engineers?

Steve Webster
*G Suite Sr Solutions Architect and Developer
<https://plus.google.com/u/0/+SteveWebster-gmail/about>  ||  SW gApps
<https://sites.google.com/site/swgapsp/>*
Google Top Contributor in: Google Apps Script, Drive, and Docs
Google Vendor (2012-2013) || Google Apps Developer Blog Guest Blogger
NEW! Google Apps Script Support Plans w/Real-time Monitoring
<http://www.swgapps.com>
G+ Community Owner: Developing add-ons for Google Docs/Sheets/Forms
<https://plus.google.com/u/0/communities/117193953428311185494>
Add-ons: Text gBlaster
<https://chrome.google.com/webstore/detail/text-gblaster-sms-texting/pbbgimdnldlfkdichlcaonmmbfnddibh?utm_source=permalink>
, Remove Blank Rows
<https://chrome.google.com/webstore/detail/remove-blank-rows/gmidogdphchbiehdmbigdbcopkpjpnio?utm_source=permalink>
and
Side Study for Teachers <https://goo.gl/z1jZds>

On Mon, Jul 16, 2018 at 10:17 AM, <buganizer-system@google.com> wrote:

>and ... I still have in stackdriver this message : Error showing sidebar  Exception: You do not have permission to call showSidebar
I don't have a magic ball but I think it can be solved. For an example, did you try "https://www.googleapis.com/auth/userinfo.profile" for the user's identity. Also look at https://issuetracker.google.com/issues/109710390

On the other hand, I have to declare the manifests manually for my add-ons, because automatically it doesn't work.

There is the manifest of the last my add-on:

{
  "timeZone": "Europe/Moscow",
  "exceptionLogging": "STACKDRIVER",
  "oauthScopes": [
    "https://www.googleapis.com/auth/userinfo.email",
    "https://www.googleapis.com/auth/script.external_request",
    "https://www.googleapis.com/auth/script.container.ui",
    "https://www.googleapis.com/auth/spreadsheets",
    "https://www.googleapis.com/auth/script.scriptapp"
  ]
}

It has a simple UI without any external data except the add-on.css file (hosted on google.com). I did not find other ways to make it work.
The sample https://www.youtube.com/watch?v=OAyIYfw0YtI

The conclusion.
We need more transparency and hard rules in add-ons publications.

The disclaimer.
My English may be too bad to understand the problem deeper.

I tried some of your oauth scopes with no result, except the validation popup ask for more rights to be granted, but the onOpen still fails to show the sidebar.

It seems that there is no clue why the message 'Exception: You do not have permission to call showSidebar"' appears, so we are kept guessing.

+1 with Exception "You do not have permission to call showSidebar" on installable trigger for google docs

Sorry for the delayed reply here. After many conversations with the engineering team it was decided that we cannot support opening UI elements (sidebars, dialogs) in onOpen and onEdit. The authorization lifecycle documentation has been updated to make it clear that you can only add menu items in those modes:

https://developers.google.com/gsuite/add-ons/concepts/addon-authorization#authorization_modes

We understand this impacts the possible user experiences you can provide and we apologize for the suddenness of the change.

OK (I suppose) all of us understand that you should balance a lot of hidden risks in this case, but... ;-)
Are there any chance to add any equivalent feature, limited in flexibility (e.g. no external html or not html at all) to keep a way to inform and present dynamic information on the side triggered by onEdit?

At this point it seems unlikely. We know a lot of folks have developed, or wish to develop, workflows that rely on this behavior, but it's not something we can support.

:'(
Thank you Eric for make this point :(sadly:) clear, and thank you and all the gapps team for your work, help and support.
J

#6 is worked for me. Thanks!

Yeah, thank you for #6. Google, this was a terrible change, I hope after all these years you'll reconsider. Just add "automatic sidebar opening" scope and let us use it.