I've just upgraded to Creative Cloud from CS5.5 and I immediately noticed my source code no longer lines up between rows.
In 5.5 if you typed four spaces and a character, then on the next line entered a tab followed by a character, the two would line up. This no longer happens in CC.
I can't go back to the old Monaco font either as Dreamweaver now antialiases the text so it looks terrible.
Is there anything I can do about this and if not is Adobe likely to fix it?
It makes my code quite hard to read at times.
It's set to 4, but changing that doesn't seem to make any difference.
The number of spaces never matches the width of the tab.
It's always out by about half a space.
Have you tried it yourself? Do you have the same problem?
We tested this further and found that there is an option in Preferences to match the tab and number of spaces.
Go to Preferences in DW CC < Code Format < Enable the option "Insert as spaces" < Ok.
Close DW and Restart.
I'm having this problem also. It became annoying immediately after installing DW CC. I'm on a Mac as well, using OS X 10.8.4. Using "Insert as spaces" seems to remove the Shift+tab command to backspace a Tab, which is just as important to me as the tabs lining up.
I tried switching the Code View and Fixed Font font using Preferences < Fonts < Code View/Fixed Font to Courier New (how it's set on my old XP computer with CS5.5, because the tabbing function works like it's supposed to on that), but it doesn't help too much. I also tried Monaco, and it's still not quite right.
The tabs still don't line up. Most (but not all, it happens randomly) of the time, new lines start one tab to the left or right, or a half space to the left. It gets pretty annoying, especially because it's unpredictable what it'll do or when it'll do it.
Any other solutions (or a bug fix would be nice, Adobe) would be greatly appreciated.
I use tabs for a reason, they let me navigate around my code quickly using the keyboard.
Replacing tabs with spaces means I can no longer move the cursor a block at a time. It also means I would have to replace all the tabs with spaces in my existing files, which I'm not prepared to do.
The "Insert as spaces" option does not make any changes in behavior of TAB functionality in DW. Its just that when you press the TAB, it will jump to a point equivalent to four spaces. You can also change the number of spaces as per your need, so that when you press the TAB it moves the cursor in blocks equal to those spaces.
"The "Insert as spaces" option does not make any changes in behavior of TAB functionality in DW. "
Yes it does, it inserts spaces instead of tabs (The clue is in the name).
If you press the tab key, you get 4 spaces instead of 1 tab.
If you then tap the left arrow key on your keyboard, the cursor will move back 1 space instead of 4.
This makes navigating around your code 4 times as slow, and makes it very difficult to indent your code properly or line anything up.
Some programmers don't use tabs, so this bug doesn't affect them, but for me it renders Dreamweaver unusable.
What I found to be useful is to go to Preferences > Code Format.
Indent [x] with  Tabs (I chose Tabs instead of Spaces in this option)
Tab Size: 4 [ ] Insert as space (I left this option unchecked)
Restarted Dreamweaver. Tabs seem to work correctly when set up this way.
Note: Using Mac OSX 10.8.4.
As far as I can tell, that's exactly how I normaly have my tabs setup, so I don't see how this helps.
The problem remains the same.
The width ratio between tabs and spaces is out by about half a space.
I had the same problem and fixed it:
Dreamweaver > Preferences > Code Format
I also changed the code view font back to Monaco 10pt - looks absolutely fine and back to how Dreamweaver was.
I'm on an almost new iMac running 10.7.5
Also - any code that you have written with CC will most likely have the wrong formatting and therefore the tabs will not line up correctly. I'm having to go through my document and update the tabbing accordingly.
Hope this helps.
Changing the font to Monaco doesn't fix the problem for me.
Could you post a screenshot of a line starting with 1 tab, followed by a line with 4 spaces, to see if they are aligned.
They definitely aren't on my system.
It appears to be a problem with how Dreamweaver is setting the width of the tabs, rather than an issue with the new typeface as I originally thought.
The logical way for Dreamweaver to work out tab width, would be to take the width of a character in the current monospaced font and multiply that by the 'tab size' setting the user has assigned. This doesn't seem to be the case at the moment.
As it stands, tabs are always a little shorter than the corisponding number of spaces, even if you set tab size to 1. If you type a line of tabs, followed by a line with the same number of spaces, the tab line will get increasingly shorter (and out of alignment), as you add more tabs/spaces.
I've worked out that if you set tab size to 10, this will actually line up with 9 spaces. So it must be out by around 10% (multiplied by the tab width). This means if you set tab size to 5, the tab will be half a character too short (i.e. 5 * 10 = 50%).
I hope this helps the developers fix this bug.
Add me into the mix. I too am on a Mac (haven't tried my PC yet), but it is highly frustrating that my code view is all messed up. Why when upgrading can you not transfer all of the preferred settings from the old version (i.e. I also had to turn off word wrap)...
Just to bump this since it wasn't fixed in the last update.
I'm another user on Mac OSX and things still don't line up.
Indent by 1 Tab
Tab Size: 4 spaces
Insert as spaces: Unchecked
Font: Monaco 10px
I have been encountering the same maddening problem for months now and finally tried resolve this matter today...to no avail. I am surprised to find this issue still remains (since it was brought to your attention June 19, 2013). I realize it is only a "Mac" problem, but Mac users are a notable chunk of your user base.
Any idea when this bug is slated to be resolved?
Hi Guys ,
We have had some hedway into this issue and have fixed this issue . You guys can expect this fix to be available in the future updates .
In case anyone is interested in having a look at this fix and try it out before that , please drop a mail to me at vharisatadobedotcom .I can help you out with the next steps