Hello,
Does DO have any start up command line options? Suppose I want to start a new lister with particular settings - say a certain font, single pane, etc that is different from the my normal settings
Is this possible?
Thanks
Hello,
Does DO have any start up command line options? Suppose I want to start a new lister with particular settings - say a certain font, single pane, etc that is different from the my normal settings
Is this possible?
Thanks
You can run any Opus command from the command-line using dopusrt.exe, like this:
"C:\Program Files\GPSoftware\Directory Opus\dopusrt.exe" /CMD <command>
You could use the Go command to go to a certain folder using a certain display mode or, easier, set up a lister the way you want it to be and then save that as a Layout.
If you call the layout "Moo" then the command-line to open that layout would be this:
"C:\Program Files\GPSoftware\Directory Opus\dopusrt.exe" /CMD Prefs LAYOUT="Moo"
Layouts can save and recreate one or more windows and will remember the directories they were showing, the display mode and folder format, and things like whether the viewer pane and folder tree are on or off.
Layouts won't remember font settings. Those can't be changed for individual windows as they're a global setting.
Thanks for the info - for some reason could not find it in the help file.
This is a constant refrain. I have used it myself.
The reason is not that you are looking in the wrong place, but that the help file is not, how can I put it, much help in many ways.
Much software will have in its manuals an entry for "command line". Not DOpus. Even the pdf file, which is easier to search, is not a lot of help.
The response you will get to such complaints is that you would need a help file the size of the Encyclopaedia Britannica to cover all of the possibilities within DOpus. This is a valid point, although it could be more helpful with some basic features, like the command line.
So, be prepared to come here when you have questions. I have found that the natives are, mostly, very helpful and accommodating, even when you are the 80th person to ask a question. (The exception is when you so much as hint that DO is less than perfection incarnate, when the fan boys can match the Macolytes with their bigotry and abuse.)
The archived forum is also good for finding things, if you can work out the right search term. And folks like (maybe only?) leo have some really neat third party reference material (read and digest his signature and trot on over to his hopelessly misnamed website, which has few signs of pretentiousness).
Sorry to ramble on, what I really, meant to say was that DOpus could use its own "wiki" site. I keep coming across hidden gems. But, not having completed my PhD course in DO, I continue to flail around. With a wiki, we could all build up a truly useful resource.
One example of a software wiki is that one for Mailwasher which is such a simple piece of kit that it hardly needs a "User-developed Knowledge Base" as Wikipediadescribes it.
We looked a while ago but could not find a Wiki which allowed round-trip conversion back into Word format. The manual needs to be in at least three formats:
Online Help (what you see when you push F1)
PDF (for printing)
HTML (for the web)
At the moment the manual is a Word document which is automatically converted into the other formats.
A Wiki has been discussed in the past and GPSoftware liked the idea of allowing people to add/improve information, but only if it does not lead to two forked versions of the manual, which is the problem.
If you find stuff that is missing in the manual just mention it and I will add it to the list. Every so often someone from GPSoftware goes through the list and fixes the reported things.
If anyone knows of a Wiki tool that allows round-trip conversions as well as moderated editing then let us know and we'll take a look at it. Being able to edit the manual easily, and allowing anyone to suggest changes, would be brilliant; it just has to be done in a way that allows conversion back to PDF, Word and the online help format. (Or just Word, since the PDF, online help and web versions of the manual are all generated from a Word document.)
FWIW, DOpusRT is mentioned in the Command Control Codes section of the manual, but I agree it is not easy to find if you don't already know it is there. (Searching for "command line" will bring up that page as the first hit, but it's actually coincidental as the text at the top uses the phrase and not the DOpusRT section, and there's so much other information before the DOpusRT section that you could be forgiven for assuming the page was not relevant.)
The only other command-line stuff you can do are DOpusRT.exe /show , which displays things with the Opus viewer (the same as running d8viewer.exe and DOpus.exe to open a window showing a given path (which you can do better with DOpusRT.exe /CMD Go , since that allows more control over how the window is opened.)
(There area a couple of other commands but they're only of interest to plugin developers.)
Thanks for the additional info.
I don't really see why the wiki has to be the "final solution". If you cannot find one with desired export facilities, it can still exist on its own, as an addition to this forum. I searched this forum on several occasions and never found what I was looking for. Wiki would definitely be a great addition
I agree, a wiki could be in addition to the manuals and stuff, and can include much of the neat material that ends up in the forums.
I really do take the point that a complete manual would fill a bookshelf.
There has been much progress in collaborative/wiki software of late.
I am involved in a government project that uses Central Desktop to share documents. It also has a wiki function.
But it does cost. There are also open source alternatives.
a wiki!?! sorry whats the address, you failed to mention it?
--
Finally a place to pick up hints and tips, woohoo.
Which wiki are you looking for?
Did you read the discussion?
The whole point of the chat is that there isn't one.
If you want to reach other wikis mention – who knows from your vague message? – then I embedded links to those I mentioned in my message.
I think miscellaneous is joking - he'd like to use the new imaginary wiki....
I come back to this with a couple of suggestions for the next version of the PDF file.
When creating the bookmarks that generate the navigation in the PDF file, how about also making the index "live," with clickable links?
Doing this individually would take time – thanks to whoever produced the existing internal links – but if you get Word to create the index, Acrobat's PDF Maker can generate a file with embedded links.
I mention this partly because the page numbers that appear in the index do not match those seen by Adobe Reader. In other words, if the index says something is on p 138, if you tell Reader to go to page 138 you actually wind up on page 130. No big deal, but adds a step in the navigation. (Just remember to add 8 to the numbers you see in the index.) If the index entry pointed to the page, problem solved.
I had a few other thoughts on the indexing, such as indexing the Internal Commands Summary, but that is probably going too far. After all, the ability to search the file – especially outside Acrobat – is one reason why I prefer it to the Help file.
Happy to help in any grunt work if it makes life easier, although I persist with Acrobat 7 as I don't appreciate Adobe's ripoff upgrade prices, which equates £ with $.
It would certainly make sense for the index at the back of the PDF to be clickable. I'll mention it to Greg.
The F1 help version of the manual has exactly the same text and already has a clickable version of the index (the Index tab within the Contents, Index, Search panel on the left).
I realise that the Help file and PDF are identical.
I wondered if that could cause problems with my suggestion for a clickable index. If the software that creates the Help file – I'm guessing that this is how you do it – gags on whatever has to happen in Word to create the appropriate gas, all hell could break loose.
I wonder if Greg ever sorted out why the PDF files created at their end wind up being protected from annotation. I gather that it isn't supposed to work like that. His guess was that it might be a new "Feature" in Acrobat 8. It certainly makes the PDF file less useful than it could be.
Fortunately, he generously sent me an unprotected version.
Yes. It seems that if one sets Acrobat 8 to restrict file access it locks all access to the document. There are settings that are supposed to allow commenting and I did have these set but Adobe obviously know best.