Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resume unreliable in some circumstances #1

Closed
oskay opened this issue Mar 23, 2016 · 2 comments
Closed

Resume unreliable in some circumstances #1

oskay opened this issue Mar 23, 2016 · 2 comments
Assignees
@oskay
Labels
bug

Comments

@oskay
Copy link
Contributor

oskay commented Mar 23, 2016

Need data: After pausing, the resume function sometimes just returns home, instead of resuming.
@oskay oskay self-assigned this Mar 23, 2016
@oskay
Copy link
Contributor Author

oskay commented Mar 25, 2016

Appears to only happen for long straight segments, not for short curvy things.

@oskay oskay added the bug label Mar 29, 2016
@oskay
Copy link
Contributor Author

oskay commented Apr 3, 2016

The behavior appears to be for straight segments that call the SHORTPATH ESCAPE. Result was that the resume node counter seemed to be off, and not resuming at the right point.

Triaged in v1.0.2, fixing the original bug, by decrementing the node counter before saving the progress. A side effect is that the last path segment before pausing is drawn twice. Will revisit this later.

oskay added a commit that referenced this issue Apr 3, 2016
@oskay
A huge amount of fine-tuning for launch time
2552570 
* Making use of newer GUI elements in the extension, for header (bold)
text, indents, and slides on pen-up & pen-down positions.
* Triage & close issue #1 with failure to resume properly.
* Pen up & down delays now calculated correctly for AxiDraw range.
* Pen up & down delays now calculated automatically.  Optional delays
are available at those points.
* Remove options to reverse motor 1 & motor 2. (Not actually needed by
end users, saves quite a bit of logic at time-critical places.)
* Make maximum speed (former 100%) now 110%, to indicate that this is
at the end of our usable range.
* Clarify error messages in case of finding off-page elements
* Fix Big Ugly bug (tm) where pen up moves were not properly limit
checking the distance before moving.
@oskay oskay closed this as completed Apr 9, 2016
@oskay oskay mentioned this issue Aug 22, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oskay oskay

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@oskay