Opened 12 years ago

Closed 12 years ago

#1667 closed defect (invalid)

xref and yref have no effect in d.vect labels in GRASS 7

Reported by: cmbarton Owned by: grass-dev@…
Priority: normal Milestone: 7.0.0
Component: Display Version: unspecified
Keywords: Cc:
CPU: Unspecified Platform: MacOSX

Description

Changing xref and yref do not affect the label positioning. No error, just no effect. Labels are placed below and to the right of points in all cases, regardless of xref and yref settings. This is OSX but probably affects other OS as well.

Change History (5)

in reply to:  description comment:1 by mlennert, 12 years ago

Platform: UnspecifiedMSWindows CygWin

Replying to cmbarton:

Changing xref and yref do not affect the label positioning. No error, just no effect. Labels are placed below and to the right of points in all cases, regardless of xref and yref settings. This is OSX but probably affects other OS as well.

I cannot confirm this with a fresh checkout of trunk on Debian GNU/Linux. Label positioning works perfectly here.

Marking this as platform-specific for now.

Moritz

comment:2 by cmbarton, 12 years ago

Platform: MSWindows CygWinMacOSX

I'm on a Mac, so I am switching the platform to that, since I can't say that it doesn't work in Windows. Are you doing this through the GUI?

Michael

in reply to:  2 comment:3 by mlennert, 12 years ago

Replying to cmbarton:

I'm on a Mac, so I am switching the platform to that, since I can't say that it doesn't work in Windows.

Sorry, meant to set MacOSX, must have been distracted.

Are you doing this through the GUI?

Both in the GUI and on CLI with d.mon start=png.

Moritz

comment:4 by cmbarton, 12 years ago

OK. I was doing it through the GUI only, but could see that the correct command was being constructed. Just a thought, perhaps this does not work in a LatLon region?

Michael

comment:5 by cmbarton, 12 years ago

Resolution: invalid
Status: newclosed

I just tried it again in Spearfish and then in the LatLong location again and it worked. I guess I'll chalk this up to to one of those mysterious errors and mark it as invalid. If I can cause it to happen consistently, I'll reopen

Michael

Note: See TracTickets for help on using tickets.