-
Notifications
You must be signed in to change notification settings - Fork 343
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
First-record scanning let trailing text be parsed as number #2613
Conversation
IN our example, the data record 0 2 -JX8cd/8c ended up giving the harmless warning -JX8c/8 not a valid number and may not be decoded properly because gmt_scanf_arg was fooled. This tightens the check.
I'm still getting a
|
Ok, which test? |
It's a Julia one.
BTW, this should be a INFO too, no?
|
and this
|
OK, please fix - going on hike. |
Odd to give differernt height and width for a square (circle) plot. I will look. psrose was the last module to actually tolerate -J. It had its own -Sradius forever. I probably am taking some short-cut and did not anticipate your crazy -J argument. |
That's automatic generated code. Must add a check to make it square by default for roses. |
OK, now that argument will cause an error on the psrose side (same for psternary) |
Why forbid? If user want to deform just let him do that. And what if a subplot with rectangular subplots want to plot a rose? A warning is fine here, but erroring is is extreme. |
Even if I use
|
Please update. |
It gives
psrose -R0/25/0/360 -JX12c/8c -Bxa10g10 -Bya10g10 -B+t"Sector -BDiagram" -: -A20 -D1 -F1 -S4 -Gorange -W1 -P -K > C:\TMP\GMTjl_tmp.ps
psrose [ERROR]: Option -J: Must specify -JX<diameter>[<unit>]
From: Paul Wessel <[email protected]>
Sent: Sunday, February 2, 2020 8:03 PM
To: GenericMappingTools/gmt <[email protected]>
Cc: Joaquim Manuel Freire Luís <[email protected]>; State change <[email protected]>
Subject: Re: [GenericMappingTools/gmt] First-record scanning let trailing text be parsed as number (#2613)
Please update.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub<#2613?email_source=notifications&email_token=AAEDF2PMZUQFL4AXBIOHV2DRA4RFRA5CNFSM4KORQJZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKR7RPI#issuecomment-581171389>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEDF2NZ76OM5QUSGGZYI2LRA4RFRANCNFSM4KORQJZA>.
|
Even if we allowed -JXa/b we are drawing the rose per polar coordinates using a radial scale. It makes absolutely no sense to give -JXa/b to prose and psternary. As for subplots, we are supposed to give a -JX? or -Jx? as the projection. Not sure if we have a test for this with rose and ternaries so that would be a good test. |
The gmtio_examine_current_record failed to distinguish text from numbers.
In an example, the data record
0 2 -JX8cd/8c
ended up giving the (harmless but annoying) warning
-JX8c/8 not a valid number and may not be decoded properly
because gmt_scanf_arg was fooled. This tightens the check.