Fixed
Status Update
No update yet.
Comments
al...@gmail.com
would be useful!
am...@google.com
am...@google.com
much needed
il...@google.com
il...@google.com
ap...@google.com
I need to monitor active sheet because I have different side bar for every sheet. What I'm doing now is running a JavaScript from the client side every 1s (second) to call google.script.run.monitorTabChange();. This function reads current active sheet's name and compares it with a sheet name that had been saved in a PropertyService during the last call of google.script.run.monitorTabChange();.
The spreadsheet with this script helps me with creating Purchase Orders. It pulls data from Salesforce and Quickbooks and generates a PO. So for every PO for every customer I am duplicating the spreadsheet and of course the script. The problem that I am facing is running out of quota. I have generated tons of POs already and each of them runs (even if the spreadsheet is not opened - I tested it) the 'monitorTabChange' function, which calls PropertyService. I have 100 000 quota for PropertyService calls. And I'm running out of it pretty quickly now.
The trigger 'OnSheetChange' would then save me (probably many others too) from this issue. At the same time it would saved Google tons of execution overhead (that could be significant if lots of people use the solution I do to track the sheet change).
Thanks!
The spreadsheet with this script helps me with creating Purchase Orders. It pulls data from Salesforce and Quickbooks and generates a PO. So for every PO for every customer I am duplicating the spreadsheet and of course the script. The problem that I am facing is running out of quota. I have generated tons of POs already and each of them runs (even if the spreadsheet is not opened - I tested it) the 'monitorTabChange' function, which calls PropertyService. I have 100 000 quota for PropertyService calls. And I'm running out of it pretty quickly now.
The trigger 'OnSheetChange' would then save me (probably many others too) from this issue. At the same time it would saved Google tons of execution overhead (that could be significant if lots of people use the solution I do to track the sheet change).
Thanks!
ap...@google.com
will really appreciate this feature :)
jb...@google.com
I'd like an onSwitchSheets event trigger with the following information available:
The sheet I'm switching from, active cell I'm switching from, active row I'm switching from, active col I'm switching from etc.
The sheet I'm switching to with ability to:
- land in a specific cell
- modify the contents of a cell or range of cells in the switch to sheet
- initiate a re-calculate in the target sheet after changes have been made.
Even better... onPreSwitch, onSwitch, onPostSwitch
Excessive code is required to implement the functionality I'm chasing without these hooks.
The sheet I'm switching from, active cell I'm switching from, active row I'm switching from, active col I'm switching from etc.
The sheet I'm switching to with ability to:
- land in a specific cell
- modify the contents of a cell or range of cells in the switch to sheet
- initiate a re-calculate in the target sheet after changes have been made.
Even better... onPreSwitch, onSwitch, onPostSwitch
Excessive code is required to implement the functionality I'm chasing without these hooks.
an...@google.com
Any news from Google team?
i Would like to re-hide hidden sheets when user leaves it
i Would like to re-hide hidden sheets when user leaves it
il...@google.com
Hey Google,
This feature is highly in need for us. Can you please respond?
This feature is highly in need for us. Can you please respond?
jb...@google.com
This trigger would also be useful for the code I'm working on.
ap...@google.com
very mandatory
an...@google.com
Needed!
an...@google.com
I need something like this too
Description
Version used: 27.0.2
Theme used: Theme.AppCompat.Light.DarkActionBar
Devices/Android versions reproduced on: Nexus 5X 8.1
If I set `setReorderingAllowed(true)` when doing fragment `hide()` and if there is a Visibility changing transition (`Fade` in my case) used as an exit on a fragment it internally sets all the views to `INVISIBLE` after the transition is over in `FragmentTransition.replaceHide`. But if you then press hardware back button, it attemts to build a list of views to fade back in, but that list is always empty because `FragmentTransitionImpl.captureTransitioningViews` always checks if they are `VISIBLE`. And I return back to a fragment with a bunch of INVISIBLE views.
- Relevant code to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).
- Steps to reproduce
Install demo app
click switch app
press back button to return to the first fragment
behold second fragment fade out instead of sliding down while underlying fragment becomes visible, but it's contents are INVISIBLE