Author Topic: NANY 2011 Release: Cautomaton (Read 93,441 times)

worstje · « **Reply #25 on:** November 16, 2010, 07:34 AM »

And now v0.8.3 is out!

Request for testers

Please give the /i:a, /i:w, and /i:u suboptions special attention. In any combination with any of the other commands. If stuff works as you expect it to, great. If it doesn't, less great, but either way, I want to hear to what extent those options work with non-standard menu items. Especially /i:w gives me cause to worry where Windows XP is concerned!

v0.8.3 (2010-11-16)

    New functionality! The tip of an iceberg yet to crash into your boat...
    
      Added: invocation now honours whether you press Ctrl and/or Shift.
      Added: popup (/p) suboptions, of the format /p:...
          @         Do not show off our trademark hat.
          XXX,YYY   Display at these screencoordinates (has to go last).
        Example: cautomaton.exe /p:@-300,500 myfile.jpg
      Added: invocation (/i) suboptions. The /i on its own is pretty much
        useless as invocation is the default (which /n cancels). A list:
          a     _try_ to do invocation asynchronously.
          w     _try_ to wait till the invocation is done (=synchronous).
          r     if possible, try to count this as a 'recent document'
          u     allow windows ui to popup where needed. This is often used for
                  errors and thus disabled by default, but also needed for
                  the 'delete' verb to popup a window asking for confirmation.
          z     no zone checks (UAC: This file comes from the internet, ok?)
          S/s   Force the Shift key into a pressed (S) or unpressed (s) state.
          C/c   Force the Ctrl key into a pressed (S) or unpressed (s) state.
      Fixed: modal dialogs running in the same thread work now. The 'delete'
        verb uses this, but for example 'properties' does not, so the holy
        grail of UI interaction has not been discovered yet.
      Fixed: the debug (/d) shows a bit more now, and less at the same time.
      Known issue: canceling 'delete' operation gives Cautomaton an unknown
        error code, which it treats as a standard failure that can only be
        recognised when running in debug (/d) mode. Can add a special exit
        code meaning 'delete canceled' if requested. Opinions please?
      Known issue: documentation still sucks.

cranioscopical · « **Reply #26 on:** November 16, 2010, 01:55 PM »

For the quintessentially lazy, it'd be neat to have an option for XXX,YYY that positions the pop-up relative to the console window.

What should I see from a console in response to, say
Cautomaton /i:a /m "Win&Zip | Add to &Zip file..." readme.txt
versus
Cautomaton /i:w /m "Win&Zip | Add to &Zip file..." readme.txt

mouser · « **Reply #27 on:** November 16, 2010, 02:22 PM »

ok let me give the new version a test

worstje · « **Reply #28 on:** November 16, 2010, 02:41 PM »

Quote from: cranioscopical on November 16, 2010, 01:55 PM

For the quintessentially lazy, it'd be neat to have an option for XXX,YYY that positions the pop-up relative to the console window.

Well, it's a pretty useless feature outside of testing and to boot difficult feature to implement (or so I think). After all, unlike other windows, console windows aren't technically created by me but are provided by Windows because it is a console app, so interacting with them is a pain. You can always leave positioning out and let it position at your mouse cursor - it is what I tend to do.

(Be happy that there's a hat nowadays, and the option to hide said hat - in my pre-v0.8.1 testing days, it'd always pop up this gigantic window that always blocked the console from view.

)

Either way, thank you both for testing. I look forward to hearing thoughts, complaints and experiences.

cranioscopical · « **Reply #29 on:** November 16, 2010, 02:47 PM »

Quote from: worstje on November 16, 2010, 02:41 PM

Well, it's a pretty useless feature outside of testing

Fair enough.

Please see #26 above

worstje · « **Reply #30 on:** November 16, 2010, 04:35 PM »

Hopefully, something. Probably nothing. Does that sound as confusing as it is?

I'll paste the documentation and let you decide for yourself... and ironically, while trying to answer your question, I just found two different documents that give rather different descriptions.

Quote from: CMINVOKECOMMANDINFO Structure

CMIC_MASK_ASYNCOK (/i:a)

Wait for the DDE conversation to terminate before returning.

CMIC_MASK_NOASYNC (/i:w)

Windows Vista and later. The implementation of IContextMenu::InvokeCommand should be synchronous, not returning before it is complete. Since this is recommended, calling applications that specify this flag cannot guarantee that this request will be honored if they are not familiar with the implementation of the verb that they are invoking.

Quote from: CMINVOKECOMMANDINFOEX Structure

CMIC_MASK_ASYNCOK (/i:a)

The implementation of IContextMenu::InvokeCommand can spin off a new thread or process to handle the call and does not need to block on completion of the function being invoked. For example, if the verb is "delete" the IContextMenu::InvokeCommand call may return before all of the items have been deleted. Since this is advisory, calling applications that specify this flag cannot guarantee that this request will be honored if they are not familiar with the implementation of the verb that they are invoking.

CMIC_MASK_NOASYNC (/i:w)

Windows Vista and later. The implementation of IContextMenu::InvokeCommand should be synchronous, not returning before it is complete. Since this is recommended, calling applications that specify this flag cannot guarantee that this request will be honored if they are not familiar with the implementation of the verb that they are invoking.

I was using the latter as my reference while developing. So not only does Microsofts own documentation seem unclear and confused on what it means, to add insult to injury the 'wait' variety is Vista+ only and FULLY OPTIONAL. The latter is most likely the reason you see no difference - Winzip probably sees no difference between the two.

Re-reading this, I am half of a mind to include what is atm known as the /i:a option and remove that one completely, leaving just the /i:w variety. The mention of DDE I see now makes me suggest it is ancient history and not so important (DDE pretty much became legacy back in w95).

And in case /i:w does not work as hoped, I intend to add a couple of 'bandaids' to handle specific waiting scenarios.

cranioscopical · « **Reply #31 on:** November 16, 2010, 07:05 PM »

Quote from: worstje on November 16, 2010, 04:35 PM

Hopefully, something. Probably nothing.

You must be prescient — that answers my next question, viz. 'What happens when I'm required to decide for myself?'

worstje · « **Reply #32 on:** December 31, 2010, 06:49 PM »

Sadly, I need to announce I won't be getting around to making a new release anymore, at least not for as far NANY 2011 deadlines are concerned. I intend to work on it in 2011 though, and take care of the outstanding issues when time becomes available, but between this and JottiQ, the latter just took way more time. Hell, it needs way more polish by nature.

I don't think the lack of a newer release from v0.8.3 will be a problem though, as the one feature that was missing is something mouser already has a solution for. (He was the one to request the app as a coding snack in the first place after all!) So hereby please consider v0.8.3 the official entry for NANY 2011.

.. And yes, JottiQ v1.0.0 will be arriving soon.

cranioscopical · « **Reply #33 on:** December 31, 2010, 08:57 PM »

Quote from: worstje on December 31, 2010, 06:49 PM

I won't be getting around to making a new release anymore, at least not for as far NANY 2011 deadlines are concerned. I intend to work on it in 2011 though

It's pretty neat already! I'll be interested in what 2011 brings.

Perry Mowbray · « **Reply #34 on:** December 31, 2010, 09:22 PM »

Quote from: worstje on December 31, 2010, 06:49 PM

So hereby please consider v0.8.3 the official entry for NANY 2011.

Thanks!

Fully polished programmes are always going to be an issue... I think it's wonderful that you've got to this point!

Deozaan · « **Reply #35 on:** April 29, 2011, 09:46 AM »

I just basically copied mouser's example in the video and configured ScreenshotCaptor to upload images to imgur using Cautomaton and RightLoad.

Thanks!

socrtwo · « **Reply #36 on:** December 12, 2011, 10:40 PM »

Is there any hope to fix the issue with the "Previous versions" choice on the context menu? I need it for my Excel recovery project...

Ath · « **Reply #37 on:** December 12, 2011, 11:09 PM »

Quote from: socrtwo on December 12, 2011, 10:40 PM

Is there any hope to fix the issue with the "Previous versions" choice on the context menu? I need it for my Excel recovery project...

Please elaborate, iow: What are you asking?

worstje · « **Reply #38 on:** February 23, 2012, 04:14 AM »

I am covering my head in shame!

I'm so sorry I missed your post dude; I don't know how I managed it exactly but I did. Worst part is... the thing you are asking about is something I had already fixed on my computer months ago, and I was under the full impression I had released it. So I left you out in the rain with no excuses whatsoever.

That said, when I saw your post two hours ago I went right to preparing a fresh release v0.9.0. You may not need it anymore, but I will post it for you and others regardless. My sincere apologies are about the only thing I can offer you to go with it. The download link is in the opening post.

v0.9.0 (2012-02-23)

    Not much new. Or so I thought. I prepared a release a long long time ago,
    or it was supposed to be part of 0.8.3 and ended up not being included,
    and in the end I had unreleased features. I've tidied it up a it and am
    now releasing this stuff... if I remember it, that is.
    
      Added: proper support for the 'Properties' and 'Previous Versions' verbs.
      Added: mentions of all new options in v0.8.3 in the /? screen.
      Added: more debug messages, in case of people having troubles.
      Changed: /i:a was removed, and is implied by default.
        It's barely supported (if at all) anyway; same as /i:w which remains
        but is equally unlikely to make a difference. If this breaks stuff
        for anyone, let me know and I will revert the functionality to how it
        was in v0.8.3.

mouser · « **Reply #39 on:** February 23, 2012, 04:18 AM »

Nice to see an update worstje!

worstje · « **Reply #40 on:** December 22, 2014, 11:35 PM »

Guess what time it is? NANY update time!

JoTo brought a little problem to my attention involving a certain program through /v, and he wondered whether I could make it work since the match and positional options were too unreliable for him to depend on due to the many localizations of the program in question. Turns out it I could work around the bug in the other program in Cautomaton, and thus update v0.9.5 was born!

Merry christmas, happy new year, have a NANYful time!

v0.9.5 (2014-12-23)

    This one deserves an update, doesn't it? Well.. it happened entirely due
    to a good friend telling me Cautomaton was not delivering the goods. He
    was right, although it technically is a bug in another shell extension.
    Thus, a work-around was born. Merry Christmas, Happy New Year, etc!

      Added: a work-around for buggy shell extensions that refuse to heed /v.
        Cautomaton now tries to invoke it a second time by scanning manually
        through the menu to find the menu item in question and retrying the
        invocation while mimicking an actual user. This method is however not
        as efficient as a verb invocation usually ought to be; depending on the
        shell extensions that are installed on a system, there could be a lot
        more activity involved in the background. Verb invocations should be
        the most reliable option to begin with, so I expect little trouble. :-)

mouser · « **Reply #41 on:** January 03, 2015, 07:18 PM »

Just played with the new features -- worked great. This is a very specialized app but it works a charm when you need it

worstje · « **Reply #42 on:** January 03, 2015, 08:18 PM »

Well, you stole the surprise away now, mouser!

For those unaware.. he's talking about the long-anticipated (by an imaginary someone, I'm sure!

) release of Cautomaton v1.0.0! It introduces the support for invoking a context menu on multiple files that I've wanted to put in there since the moment I started implementing Cautomaton several years ago.

Thank you to mouser for testing v1.0.0, for organizing NANY for yet another year, and to everyone else I say... have a good 2015!

v1.0.0 (2015-01-03)

    Over four years have passed - most of which consisted out of my eternal
    procrastination - but at long last, magical version v1.0.0 has come. Who
    ever said Cautomaton was in eternal beta? Not me. (It was implied, though!)

      Added: the long-awaited support for multiple files!
        The first file listed is the primary source for the context menu that
        will be loaded. This matches the normal Windows behaviour: the one you
        right-click on determines the way the context menu is built up.
      Added: support for files in arbitrary locations. So now you can create a
        context menu that applies to "D:\Donkey.txt" and "E:\Elephant.bmp".
      Known issue: Windows versions prior to Vista may have odd-looking menu's
        when dealing with multiple files. Menu items may be missing, doubled
        and/or placed in weird positions. I _think_ this may not happen any
        longer, but I lack (the will to set up) a proper test environment for
        such old OSes at this time. This issue should not affect invocation
        that relies on verbs or text matching; as long as the items appear
        somewhere invocation should still work.
      Added: yet more debug messages (/d). Most are of a very technical level
        and inspired by the above features, but in case of problems these might
        just help one find a cause (and maybe a solution) for an issue they are
        experiencing.

cranioscopical · « **Reply #43 on:** January 04, 2015, 01:51 AM »

It's nice to see one here

Just had a quick play with the new version (nearly said 'it' but IainB might have caught me out).
Didn't manage to break anything so far, contrary to real life.

worstje · « **Reply #44 on:** January 04, 2015, 07:31 AM »

If it had broken, I'd blame Windows XP. Buggy piece of #@$%#$%. Ahum...

Thanks for giving a whirl. Duly appreciated!

worstje · « **Reply #45 on:** January 21, 2015, 04:43 PM »

Yet more updating... but this one doesn't really matter (unless you are like me and are really attached to the old hat...) as it only involves licensing and legalese-esque little details.

Oh, and I added a little blurb in the ReadMe on how to get started using Cautomaton, so I suppose there's that, too.

v1.0.1 (2015-01-21)

    Absolutely nothing changed! Except all the stuff that matters...

      Changed: ReadMe.txt has had a huge makeover. There is now a tutorial
        as well as a clear statement regarding the license.
      Added: The version history now has its own file in Changelog.txt.
      Changed: the Cautomaton icon has been changed because the licensing for
        the old icon is unclear with regards to commercial use. (Hopefully, its
        author will respond to my inquiries at some point in time, because I
        already miss the awesome hat!)

cranioscopical · « **Reply #46 on:** January 22, 2015, 02:30 AM »

Quote from: worstje on January 21, 2015, 04:43 PM

a little blurb in the ReadMe on how to get started using Cautomaton

chashnniel · « **Reply #47 on:** April 23, 2019, 06:38 AM »

Very great tool.

All the English commander works well.
Unfortunately it seems doesn't support unicode. Even though I can use the alternative method --- ID #136 or index 3/-7 etc. But this way is not stable.
Any solution??

chashnniel · « **Reply #48 on:** September 03, 2019, 10:46 AM »

https://www.nirsoft.net/alpha
#TraceMenuID
Nir's new tool may expand this software's feature?