Unable to use offset tool via command line

In the past you invoked the offset tool by typing the letter O in the command line. It then asked you for a distance which you could enter and then click the direction of the offset. For some reason with 2.2.1.3-12 none of this works anymore.

Any help would be greatly appreciated.

Hi SIFPD_Admin,


 // offset
        {
            {{"modoffset", QObject::tr("modoffset", "modify - offset")}},
            {{"mo", QObject::tr("mo", "modify - offset")},   // - v2.2.0r2
                {"moff", QObject::tr("moff", "modify - offset")}},
            RS2::ActionModifyOffset
        },

So, it has been modified to have the prefix "mod"(for modify), and with "mo", "moff" short commands.

You can define your own aliases, of course.

SIFPD_Admin wrote

In the past you invoked the offset tool by typing the letter O in the command line. It then asked you for a distance which you could enter and then click the direction of the offset. For some reason with 2.2.1.3-12 none of this works anymore.

Any help would be greatly appreciated.

OK, but when you use 'mo' it still doesn't offer you any way to enter the offset amount. How do you enter the offset amount via command line after the 'mo' command is entered?

Anyone?

hm... interesting, it seems that offset value may be specified only via Tool Options toolbar and not via command line.

As a workaround, you may just use "move" command (with keeping originals) - or, if you on 2.2.2-alpha - another command that is closer to "offset" - named Duplicate.

I agree. It seems the modifications to the command have eliminated the ability to enter the offset from the command line, which would be a productivity backslide. Hopefully I am wrong and we are just missing something...

This feature can be added: to specify values in the by command line.

Say, to support commands like:

mo 10

mo
10

SIFPD_Admin wrote

I agree. It seems the modifications to the command have eliminated the ability to enter the offset from the command line, which would be a productivity backslide. Hopefully I am wrong and we are just missing something...

@dxli
yes, you're right. Actually, I plan to complete current features I'm working on and review support of command line in commands as well as cmd widget itself