Simple picture viewer

O

omega

Widya Santoso said:
Any suggestions for a particular editor I could try? There's the
<shift>+<right mouse click> method, which doesn't allow you to type any
extra information. I also tried the "Associate with" command that comes
with Window Commander (shareware).

The shift-openwith | always-use dialog, that does insert a %1 by default...

I don't trust it the full 100%. Don't really know the details of the
stories: but, on some systems, it gets a hairline fracture or something,
becomes slightly unpredictable, starts adding mismatched chars and whatnot.
Mainly right now, since the association is not working right, it'd be best
to get direct view & edit access to the reg'd command entry. Oh, and the
primary problem with shift-openwith is that it cannot go beyond setting
one default association, cannot aid those times when it's more appropriate
to add actions as extra context choices.
I think I tried that one time with Windows Commander but it didn't work,
so I gave up on that- I wouldn't mind trying again, I could have made a
mistake.

I don't if Windows $Commander inserts the %1 or not.

Reviewing various context menu editors yesterday, I became conscious that
the majority in fact fail to insert %1 automatically. When using them to
add or edit a command entry, you have to type that in yourself.

As to which association/cntxt editor to recommend. Well, I took some
pictures, and reviewed how many steps you'd have, and related, with
about eight or so of them. And... The one that is most direct and
fastest for this task, it is...forbidden. I mean that it is quite
arguably not freeware.

http://www.redshift.com/~omega/2004/payware/shellxpertQ.htm

You don't have to worry about any temptation towards ShellXpert, in
any case, if you are not using 9x (that's evidently the extent of its
compatibility). Can you tell me which OS you are running? I'm going to
go back to round up a few comments/pics on some of the other context
editors, the freeware ones, and it would be good to know if I should review
their docs for statements regarding 2000/XP compatibility.

.. . . .
!NEWSFLASH. While I was messing with this, I discovered a new pickiness
that Stormview has. In earlier post, I said that it doesn't hurt to add
quotes around the "%1" parameter (and some programs need that). My results
were fine both ways, when I tested at that time with Stormview.

But today, new results. Maybe the difference has to do with the fact that
this time the Stormview app was on a different drive from the images I was
asking it to open, or something, don't know, didn't examine variables in
detail. The info of more immediate use is this conclusion:

To keep Stormview happy, you must have the %1 at the end -- and the %1
must _not_ be surrounded in quotes.

So, again, you need to get edit access to the command entry. The Windows
filetypes dialog thingy is kind of a mess, since you cannot easily find
the pertinent filetype name. That's one of the ways the independent editors
are better. They let you tell them the extension, here .gif, and then they
jumpt to the right filetype. On my system, for instance, the corresponding
filetype is named something like Irfanview.Gif.

That said, you could always go ahead and try it, the Windows dialog,
scroll around for what sounds like the name for your gif filetype, then
poke through the dialogs, until reaching the OPEN / Storm command, then
reset that to have a %1 at the end, and no quotes.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top