Thu Jun 30, 2016 9:30 pm Post
Fri Jul 01, 2016 1:04 am Post
Fri Jul 01, 2016 9:21 am Post
Fri Jul 01, 2016 9:02 pm Post
Fri Jul 01, 2016 11:32 pm Post
Sun Jul 03, 2016 10:51 am Post
Indeed, the binder is saved to the drive only occasionally. So the string we read back will not track the binder's moment-to-moment changes, but will nonetheless be our script's most detailed map of the project. Nor would a scripter have much luck in navigating the binder through recognition and clicks, as an interactive user does. Instead, he'd automate binder travel via the Previous Document, Next Document, and Enclosing Group commands, most likely.derick wrote: Reading the Binder directly is an interesting idea - the XML structure looks pretty clear (and maybe it's documented somewhere?) but I'm at a bit of a loss as to how one might coordinate keep track of the relation between the current UI state and the Binder to make sure AS is scripting clicking in the correct places etc.
In total there are 3 users online :: 0 registered, 0 hidden and 3 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 3 guests