It works flawlessly but I was wondering the stand alone viewer is it possaible to view more than just one file? I noticed that it has the forward and back buttons and with the mouse buttons too.
Though when I highlight a load of pictures and choose the DOpus imageviewer it only displays one.
any help would be great-ful.
Have you checked the setting:
Preferences / Viewer / Standalone Viewer / Generate Next/Previous list automatically on double-click
?
that is ticked, not sure whats happening? I haven't set DOpus to replace explorer but shouldn't think it be that
Are the images in a zip file ?
Is the problem that the Next/Prev list is empty and you can't jump to other pictures that were selected?
Or do you mean that you want to select several files and click a button to open each of them in a separate viewer window, so you can see them all at once?
greyed out. I highlight a few pictures like jpg files and choose the -stand alone- viewer to open them but only one is displayed which is what it should do but the back and forward buttons are greyed out. I should be able to move to the next picture in the viewer but I can't.
How are you opening the standalone viewer?
Yep worked fine, I didn't have the option clicked for all register file types.
Thanks to JohnZeman for the tip.
By the way is there a way to change the setting for next/pre pic to use with the arrow keys rather than with the mouse or space bar?
I don't think so, you could file a feature request for it though.
FWIW I generally use the mouse wheel to scroll through images.
I'm usually using an external viewer (IrfanView), but sometimes I need to use Opus standalone viewer for pictures with Unicode filenames, thus this option is not an option for me.
How is it possible to instruct Opus to automatically generate a list, even if I only use the Show Picture lister button (without resorting to the aforementioned setting)? Is it possible to modify the default Show Picture button behaviour? I didn't see any relevant argument that could be associated with the Show command.
If the only reason you want to use the internal viewer is that Irfanview doesn't support Unicode filenames then you should be able to solve that problem by changing whatever launches Irfanview to use the short (8.3) filenames instead.
If this problem with double-clicking on a 'recognised/unrecognised' pic is a Viewer problem, then this setting should be in the Viewer settings area. Double-clicking is hardly a 'special feature' of DOpus, and the 'File Operations/Double-click on Files' section seems to be a 'Miscellaneous' area containing things that do have separate areas where they would be more appropriate. IMHO
It's not really a "miscellaneous" area - they are all options that are involved with double-clicking on files. Yes the "Use internal picture viewer" could conceivably go in the Viewer section, but the other options would all still need a home and to me at least it makes more sense to keep them together.
Or to offer this setting in more than one place?
Or would that confuse the heck out of people?
Dunno, you tell me. Maybe it should be on every page in the Preferences just in case it's overlooked? 
Is that the usual response to such suggestions?
It seems to me to be reasonable to make life easy for users by putting things in places where people will find them.
If that isn't the idea when it comes to design the user interface for DOpus, fine.
Sorry if you found my answer a little facetious. In my experience, there are users who will not find an option no matter where it is located. That's why we added the search field to Preferences - unfortunately, many users seem not to find that either.
I guess that is why I persevere with my suggestion that a better manual and/or on-line KnowledgeBase would be a good way of dealing with the wilfully perverse of us who refuse to look in the right places for settings.
A quick search through the PDF file is not, I'm afraid, very helpful, even when I knew what I was looking for.
I still believe a good wiki could do a lot for users who do not want to sit exams in DOpus.
Very few people would look in them, though.
In this case, if you search either the manual or the Preferences dialog for Viewer you'll find the page you want. (Granted it's the 20th match in the manual's online help, but it's called "Double-Click on Files" which should draw one's attention to it.)
Who is going to write the Wiki you suggest? People like me already write FAQs when we have the time and think something is unclear and could do with explaining, and that adding the FAQ won't dilute the other information there too much. (Many people clearly do not even read all of the FAQ titles let alone the information contained in them, so adding more information isn't always the best thing to do.)
If someone else writes a good FAQ we can move it to the FAQs forum as well. Anyone can post into the tutorials forum. Almost nobody is doing either, so I don't see how having a Wiki would magically improve the situation. The main problem with having a Wiki version of the manual is keeping it in sync with the PDF and F1-help versions; if the Wiki is a completely separate document then I don't see what the major advantage to it would be versus what we already have with the FAQ and tutorial forums. Just having a wiki won't bring Wikipedia-level numbers of contributors and expertise; it'll just make things slightly easier for the handful of people who already contribute information here.
As it happens I've recently been given the ability to edit the Opus manual. While it isn't quite as convenient as editing via a Wiki (I have to load Word, make sure nobody else is editing it and so on), the main reason I haven't done lots of editing yet is time.
I'm sure other people would make edits as well if we had a wiki, but I doubt very many people would. As it is people can (and do) suggest edits and post edited/updated versions of pages to GPSoftware which get incorporated into the manual in time. Not many people do, though. IMO it really is a people/time/resources problem and not a technological one. And so few people read the manual, FAQs and tutorials as it is. (Not to mention browsing through Preferences to see what's there to get an idea of what can be configured and from where.)
