gnuradio icon indicating copy to clipboard operation
gnuradio copied to clipboard

grc-qt pointer arrow does not point into rotated blocks

Open chrisjohgorman opened this issue 1 year ago • 5 comments

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

  1. Create a flowgraph with a block that is rotated so it is perpendicular to other blocks in the flowgraph.
  2. The connection arrow that points into the rotated block doesn't point into the block instead it points in the direction of the block before rotation or out of the block that the connection is going into. qt_arrow_pointer qt_arrow_pointer1

Relevant log output

No response

chrisjohgorman avatar May 16 '24 13:05 chrisjohgorman

Nice, thanks for the report! And all the other high-quality reports, too, by the way!

marcusmueller avatar May 16 '24 14:05 marcusmueller

You're very welcome Marcus. I can report them. I don't know how easy it will be to fix them.

chrisjohgorman avatar May 16 '24 14:05 chrisjohgorman

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 :)

marcusmueller avatar May 16 '24 16:05 marcusmueller

@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?

willcode avatar May 16 '24 20:05 willcode

I take it back. This fix was before 3.10.10.0.

willcode avatar May 16 '24 20:05 willcode