-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
grc-qt pointer arrow does not point into rotated blocks #7343
Comments
Nice, thanks for the report! And all the other high-quality reports, too, by the way! |
You're very welcome Marcus. I can report them. I don't know how easy it will be to fix them. |
For a lot of them, the workload is really finding them, taking note of them (if you sit down and say "I'll improve GRC today" without notes of what you need to tackle, you'll not be likely to fix the things that people care about, too easy to lose oversight over what is outstanding), prioritizing, and then sitting down and fixing them. The "fixing" part isn't necessarily the hardest nor the most time-intense one there! That's why contributors that write bug reports, with explanations, screenshots if applicable, and an honest assessment, are so valuable. Sure, we got limited developer time (both in terms of paid contracts, which were really important in getting grc-qt to where it is now, but have not historically covered the majority of work on it!, and in terms of volunteer developer "after hours hours"), but having time and not knowing what to fix is worse than that :) |
@chrisjohgorman I think this was fixed in #7207, which has been backported to 3.10 after the 3.10.10.0 release. Could you see if that addresses the problem? |
I take it back. This fix was before 3.10.10.0. |
What happened?
The arrow pointer that points into a block does not point into blocks properly when they are rotated.
System Information
OS: Arch Linux
GR Installation Method: Source
GNU Radio Version
3.10 (maint-3.10)
Specific Version
3.10.10.0
Steps to Reproduce the Problem
Relevant log output
No response
The text was updated successfully, but these errors were encountered: