Fixed
Status Update
Comments
jk...@google.com <jk...@google.com>
ja...@tvh.com <ja...@tvh.com> #3
This has always been a limitation of the hybrid debugger AFAIK. Stepping out to a java function from lldb basically requires resuming the process from lldb's perspective. We don't have functionality to stop in the expected place in the java debugger after that though.
The current behavior is depends on the last action taken on the java debugger. If it was a step, then after resuming in lldb, the java debugger will stop as it normally would with just the java debugger active. If the java debugger was resumed (or just attached), then it will just continue until the next breakpoint.
I doubt we can really fix this for 2.3, but we may be able to better indicate what is going on in some cases (maybe put a warning if you step-out and land in an art function, but that kind of thing is brittle).
The current behavior is depends on the last action taken on the java debugger. If it was a step, then after resuming in lldb, the java debugger will stop as it normally would with just the java debugger active. If the java debugger was resumed (or just attached), then it will just continue until the next breakpoint.
I doubt we can really fix this for 2.3, but we may be able to better indicate what is going on in some cases (maybe put a warning if you step-out and land in an art function, but that kind of thing is brittle).
ko...@gmail.com <ko...@gmail.com> #4
Contents scrubbed on user request by admin.
fe...@gmail.com <fe...@gmail.com> #5
ชอบค่ะ
vi...@gmail.com <vi...@gmail.com> #6
No comment.
di...@gmail.com <di...@gmail.com> #7
[Deleted User] <[Deleted User]> #8
Hey I didn't do this my wife put all this stuff on my account wtf how do I delete it or see who's tracking me
[Deleted User] <[Deleted User]> #9
Put it BK to normal meaning like new
ma...@infinityvision.eu <ma...@infinityvision.eu> #10
MD SUMON
an...@gmail.com <an...@gmail.com> #13
Fingerprint and isu
bj...@edlisten.com <bj...@edlisten.com> #16
Still an issue:
DocumentApp.getActiveDocument().getBody().clear(); produces the error: "Service unavailable: Docs"
DocumentApp.getActiveDocument().getBody().clear(); produces the error: "Service unavailable: Docs"
ko...@gmail.com <ko...@gmail.com> #17
This method appears to be working correctly now. I wasn't able to replicate the "Service unavailable: Docs" error. If you can isolate the cause please let me know.
bj...@edlisten.com <bj...@edlisten.com> #18
Problem is fixed
DocumentApp.getActiveDocument().getBody().clear(); is now clearing the document without an error. Thank you.
DocumentApp.getActiveDocument().getBody().clear(); is now clearing the document without an error. Thank you.
Description
I need a method to clear a document to recreate it. I'd rather not delete the entire document because there are various links to it so I want it to keep it's ID.
I now do this using the following function:
function clearDocument_(document){
try{
while(document.getNumChildren() > 2)
document.removeChild(document.getChild(1));
} catch(e){
}
return document;
} //clearDocument_
But I think a document.clear() method would be more efficient.
Notes:
Provide any additional information which might be useful here.