I know I somehow screwed this up editing my context menus, but I can't get it back. No documents or text files or excel files will open with a double click anymore. Anyone have a tip on what I may be overlooking.
Surely you must have made a backup of your Opus settings before modifying 
...?
I would suggest you start to fix by finding these file types in the Opus file type editor (Settings->File Types...) and then deleting whatever is there on the Events tab for the Left double-click event. This should cause whatever the default 'action' is which you can then confirm on the Action tab. For most offic efiles likes .DOC this should be Open. The default Open action for .DOC files on my system with Office 2003 is a DDE Command that runs:
Application: "C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE" /n /dde
DDE Message: [REM _DDE_Direct][FileOpen("%1")]
AppName: WinWord
Topic: System
What's your's say?
This post might also be useful: [url]https://resource.dopus.com/t/can-not-open-txt-files/1417/1]
If the above advice doesn't fix it, hold shift and right-click one of the files that won't open. Go into the Open With menu and select Choose Default Program (or similar; depends on the OS version). Then choose Word and it should re-write the appropriate registry settings.
If even that doesn't solve it then you may need to repair the Word installation.
Before trying anything in my post, do try what Steje and Christiaan suggested, though. What I've written here may not be necessary.
Well, thank you guys, we're definitely onto something with the file groups, as my left double click for all file types in the document group is "not defined." But Steje, my dialog box seems different than yours, though it does say under actions "Open - C\programs... office 12, then I have type as MME - application/vnd.ms-excell or word or whatever is in the office group. When I go to events, it won't let me delete the "not defined." when I try and edit it there's not a simple "open" command in the DOpus commands options. It does have open/folder. When I just type "open" in there anyway. I get a windows error. ?
I think 'not defined' is default for left doubleclick - than the default action will be fired. You can chose a default application also within the File Type Editor. Click on the File Type and then click on Change. I found that it might not work to change the actions for a file type if you have no admin rights on XP.
Yes, it's normal for filetypes to have nothing defined for their Left Double-Click event.
Those events are specific to Opus and let you change what happens when you double-click files in Opus without changing what happens in other programs.
When the event is not defined Opus will open the files using the system-wide settings, which usually means the Open action unless it's been overridden using the Open-With menu.
Yeah sorry... since I went to the bother of explaining ANYTHING, I should have mentioned that the left double-click 'event' SHOULD be 'not defined'... and that without something specific otherwise being set, the rest of what Leo and Vitali and I explained about things defaulting to the default 'action' (usually 'Open') would then hold true...
You can try what Leo suggested, but before you bother changing anything I'm curious... does ANYTHING happen when you double-click? Does the same problem happen in Windows Explorer? If you're reasonably sure things "broke" when you were modifying your context menu, what sort of changes were you making at the time? In either or both Win Explorer and Opus, what do you see when you ckick right mouse button on the DOC files? Do you see an 'Open' item at all - and if so, is it 'Bold' in either or both Explorer/Opus? If you see it, what happens if you select it?
From the info in your reply, it sounds like you're running Office 2007 (whereas I'm running 2003). There's no way I'm ready to violate my PC with 2007 to see what the proper settings should be. If things are ALSO busted in Win Explorer, you might search around here for other users that could give examples of what things should look like for that version of office, or see if a 'Repair' of the office installation might set things right (not actually sure if the office 'repair' installations fix 'context menu' / shell related things tho)...
I've got Office 2007 installed. Here's a zip with screenshots of all the settings for the .doc filetype so you can compare them with what you have:
Doc_FileType.zip (679 KB)
Oh thank you guys so much.
To answer your questions Steje, I can double click these "document" files in windows explorer and they open. When I right click for context in DOpus, my context menu offers the choice of "open" and if chosen it works.
The double click to open in DO quit when I was altering context menus, though I may have been fooling around with file types. I was pretty new to the software at the time.
Sooo, lets see. I ques I'll study the screen shots Leo most generously uploaded.
What happens if you try to open a docx file?
docx is the new Word file type. If you don't have any, create one and see what the symptoms are for that file type. (You cannot, it seems, simply rename an existing.doc file. Word barfs.)
I suggest this because you may have done something to upset .doc files while .docx are untouched in the fiddling about.
This could be one way to narrow down the source of the problem.
At a quick glance, on my system the settings for the two "System File Types," as displayed in DO, are identical.
Unlike you, I see the correct behaviour.
If my screenshots don't help find the difference, use my FileTypeDiag tool to dump your registry settings in detail and attach them to a private message. I'll see if I can work out what's going on from that.
(Just type ".doc" into the tool's extension box and it will output a text file to the location that you choose.)
Thank you, well first my screen shots match Leo's screen shots perfectly... I'll get on the rest here in just a bit. This is the most helpful forum I've ever addressed, thanks again.
I'm going to file a bug report... I've reproduced your problem... 
.
I don't know why this happens or 'when' it may have broken... it's quite WEIRD... but I was testing to confirm the syntax for having you MANUALLY add the proper action command to the Left double-click Event in order to force Opus to 'open' the file (which incidentally, is FileType ACTION=open)...
- I confirmed it worked
- I then "DELETED" it (thereby resetting it back to < not defined >)...
- PRESTO, double-clicking DOC files just has me staring at the screen now.
HOWEVER, this only happens if you "DELETE" the actual command text you added from INSIDE the command edit window (i.e. click on the Edit button while the 'Left double-click' Event is selected, and delete the FileType ACTION=open text from inside the Edit 'dblclk' action for type: Microsoft Office Word 97 - 2003 Document dialog window)...
If you do the 'normal' thing and instead hit the Delete button on the Events tab dialog (next to the 'Set Default' button), then things still work ok and will NOT break.
They both appear to accomplish the same thing you say - and reset the Left double-click action to < not defined >... which to all of our eyes 'seems' to be fine? Yeah, I said it was weird 
.
The REALLY odd thing is that neither the info in /dopusdata\FileTypes config files or in the registry data dumped by Leo's FileTypeDiag tool seems to have changed... This is made even more 'odd' by the fact that restoring an older Opus config backup (check my signature folks...) ALSO fixes things. So I'm not sure what/where Opus seems to be "losing" track of things.
The good news is that you should be able to effectively "fix" things now by adding that FileType ACTION=open command to the double-click Event and be good to go... Actually, for that matter you could even type gibberish into the command edit window for that event, save/OK out of the command edit dialog, and THEN hit the Delete button with the Left double-click event highlighted on the Events tab dialog in order to set it back to normal (rather than leave the FileType ACTION=open command in there)... This is probably the better way, as it should leave things in truly the default state; and suggests that 'breaking' things by deleting the TEXT in the command edit window is leaving that Event running some kind of NULL command or something, even though it says < not defined >.
I'm "working" still right now, and will write up the bug report a bit "later" unless someone else beats me to it... but I would imagine anybody should be able to reproduce this now.
very interesting, steje!
Leo, for some reason, it's not allowing me to add attachments to your pm. I have the output doc ready but the browse for attachment window stays open about 3 seconds. It seems it may be planned that way.
Did you try the "good news" bit from my post yet? Does it work now? Since I "seem" to have broken things the same as you - I highly doubt your attachment will reveal anything.
Actually, I was wrong... (duh). There definitely is a "difference" - a new file get's created /dopusdata\FileTypes\Word.Document.8.oxr...
Whose contents after "breaking" things is:
<?xml version="1.0" encoding="UTF-8"?>
<xml_registry_redirect hive="HKCR">
<key name="Word.Document.8">
<key name="opus">
<key name="dblclk">
<key name="opusflags" />
<key name="command">
<value name="@default" type="sz_multi" />
<value name="OpusFlags" type="dword">0</value>
</key>
</key>
</key>
</key>
</xml_registry_redirect>
Whose contents after "fixing" things turns into:
<?xml version="1.0" encoding="UTF-8"?>
<xml_registry_redirect hive="HKCR">
<key name="Word.Document.8">
<key name="opus">
</key>
</key>
</xml_registry_redirect>
So:
a) it sure looks like the bit above implies Opus is running 'null/nothing' action once things have 'broken'
b) to the list of "fixes" mentioned above, you can probably also just:
- delete the /dopusdata\FileTypes\Word.Document.8.oxr file
- Exit Opus (from the system tray icon menu->Exit)
- re-launch Opus (shortcut, desktop dbl-click, etc)
Unless you've got other Opus specific customizations you want to keep for that FileType, that file wouldn't normally even be there...
UPDATE: Leo has already reported the bug to GPSoft... Can't keep up with him, guy is like the WIND!
Either way...
- easy to fix
- great reason to read my "signature"...
IN THIS DAY AND AGE, DEATH TO ALL APPS THAT DON'T LET YOU BACKUP/RESTORE THEIR SETTINGS 
steje, you are a hero 
or are you a professional software tester?
Good grief. Is Sherlock your middle name?