Dreamweaver MX (6.0) Forum

I have Dreamweaver MX installed and it works reasonably well except for two things:

1) Occassionally, when I switch to another app and the switch back to DW, a number of my keyboard keys no longer work; most noticibly the cursor movement keys (arrow keys, home, end, pgup, pgdwn).

2) Whenever I access either the Help or Command menu I receive what appear to be Javascript errors. The errors seem to indicate some issue with accessing the Dreamweaver Extensions part of the application. If I click "Ok" a few times I'm able to get past the errors and use the menu I clicked on.

Any ideas? Thanks!

Matt Welch

I have one idea regarding your first issue. I had a similar issue using a window manager called kahakai. Switching back to KDE fixed it up nicely. The issue in kahakai was that when I switched from window to window (using CTRL-ALT-[number]) it would leave the ctrl key stuck down (it thought so, at least). I fixed it by hitting the ctrl and alt keys a few times until I had full control again. Of course, I had to do this EVERY time I switched away and switched back to the app, so I ended up giving up kahakai soon after realizing what the issue was. This was in crossover 2.1, I think.

Regarding your first issue, what desktop environment are you using? I have found in the past (running Fedora Core 2/Crossover 3.0.0) that when in Gnome Dreamweaver would exhibit odd keyboard behaviour as you describe - cursor keys don't work, backspace is the equivalent of 'undo' etc. I had no such issues under KDE though - if you have access to both you may want to try and see if that solves your issues. Might be something to do with the way Gnome handles keyboard events...

Can you tell us what javascript errors you get on these menus, and if you get them anywhere else? Are they consistently reproducible? Some more details on your system might throw something up as well... Otherwise, check the errors for the path they refer to - I've had issues with other apps that use inconsistent capitalisation - of course, not an issue under Windows, but is in Linux. If it looks like there are inconsistencies, you may want to create a link to the offending directory with the required caps. For example, if there are two pieces of code referring to 'Header/header.js' and 'header/header.js' (don't know if there is - just a random example), then execute;

ln -s Header header

(Assuming 'Header' exists already and 'header' doesn't).

Hope that makes sense, and can be of some use!

Cheers,
Peter