exit on bad geometry

[dacyberduck]

When geometry argument received is invalid, prevent wf-recorder from recording rather than setting geometry to default '0,0 0x0' and continue recording.

[soreau]

Maybe have the output message suggest that the geometry might need to be in quotation marks, too?

[dacyberduck]

Maybe have the output message suggest that the geometry might need to be in quotation marks, too?

That is already mentioned in the documentation as well as '--help' text. Adding something like 'see: wf-recorder --help' to the message should suffice.

[soreau]

Maybe wf-recorder --help | grep geometry or even more direct: Bad value of geometry: %s\nDid you forget to wrap it in quotation marks?

[dacyberduck]

Maybe wf-recorder --help | grep geometry or even more direct: Bad value of geometry: %s\nDid you forget to wrap it in quotation marks?

Well, we can't simply assume that the value is wrong only because it is not properly quoted. Maybe the user has given a completely wrong data that doesn't represent any geometry.

[soreau]

The reason I suggest the message suggestion is because 1) the number one reason this happens is because people forget the quotations and 2) a message telling people to look at --help output isn't very useful when it's not clearly spelled out that quotations are needed there. Maybe we could combine the ideas and suggest both --help and ask if the argument is not quoted?

[ammen99]

I agree with @soreau, it would be nice to directly print an example of how to set the geometry and say it should be quoted.