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.

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

Print - cursor presentation bug #740

Open
bobgates opened this issue Dec 13, 2019 · 1 comment
Open

Print - cursor presentation bug #740

bobgates opened this issue Dec 13, 2019 · 1 comment
Labels

Comments

@bobgates
Copy link

bobgates commented Dec 13, 2019

Environment:

Describe the bug
When using the print button with the oscilloscope, the cursors are appearing as very thin ticks perpendicular to the line (see screenshots). This doesn't make clear what they are. It seems like the tiny ticks are actually the scales that should go vertically and horizontally in the middle of the screen, but they're being drawn where the cursors and/or the triggers are.

To Reproduce
Steps to reproduce the behavior:
Click on Print Button

Expected behavior
An image/pdf that looks more like the Scopy screen at the time

Screenshots
Screen Shot 2019-12-13 at 09 10 18

See annotated PDF below for the problem, based on printing the screen shot above.
[Scopy-osc-2019-12-13-09-09-38_edited.pdf]
(https://github.com/analogdevicesinc/scopy/files/3960133/Scopy-osc-2019-12-13-09-09-38_edited.pdf)

@bobgates bobgates added the bug label Dec 13, 2019
@bobgates
Copy link
Author

bobgates commented Jan 3, 2020

I've been digging and found that this occurs when the graticule is switched on, and is in fact the two halves of each of the graticule axes printing at two places on the screen, neither where it should be. It doesn't happen on the screen, only when printing. It is related to how the code works out where to put the graticule.

I'm digging into it, hope to have a solution soon . . .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant