DreamWeaver CC 19 isn't just slow, it's pants-on-head ret*rded with larger files

[Christopher Liam Ivey]

I'm trying to edit some big .css files, (about 400 KB).  I only have one file open.  If I try to edit text, each keystroke takes between 15 and 30 seconds to register.

Does anyone have any suggestions?  It's a new, clean install, and seems to work fine with small files. 

[Jon Fritz]

Any chance there are any structural defects in the code? (You can check it here)

Newer versions of DW tend to be much more sensitive to code errors than older ones.

Are you editing the .css file directly, or through the Related Files Bar of a .html file that it's attached to?

[Christopher Liam Ivey]

The code is from a commercial template.  It's bulky, but it renders just fine, and very quickly in any browser you choose to test with, with no errors showing in the property inspector.  I am editing the code directly - opening only the .css file.  Searching within the code is really slow, and edits are impossibly slow. 

I'm going to try to download Sublime and Visual Studio Code and give those a whirl.

[osgood_]

A commercial template which needs 400kb of css should be assigned to the bin, regardless of whether DW can handle it or not. In this case its doing you a 'favour', alerting you to bloat, on a huge scale.

[Christopher Liam Ivey]

That's not my choice, so this is not a helpful reply. I have to work with what I'm given and don't have time to rebuild an entire template system written by heaven only knows who.  I just have to make it work.

For now, I'm using a trial of Sublime Text which seems a little nicer than Notepad ++.  I'd love to use Dreamweaver, since I'm paying for it, but if resolving this isn't simply a matter of changing a setting or making a quick fix, I can't spend any more time on this issue.

[Christopher Liam Ivey · Accepted solution]

Thanks everyone for your replies, even if this remains unresolved.  I can't see any button to mark this thread as closed, but from my perspective this question is answered.

[osgood_]

Agreed, its not the most helpful of replies, just an honest one about the state of web-development these days. Unless you ARE prepared to control everything yourself then you don't really know what crap you're getting yourself involved with.

You can't mark an answer as correct/resolved, one of the monitors have to do that. I have no idea why, that should first and foremost be the domain of the poster. Only IF they don't mark a post as resolved should the monitor then interpret what is correct or near to correct.

I thought this feature was being bought back to the forum on request.

Anyway good luck with your project.

[Christopher Liam Ivey]

Oh, it's definite crap I'm dealing with.  CMS templates have become a bloated, horrible mess, with mutiple layers of foundations, each overriding the CMS of the last.  So much duplication.

[Nancy OShea]

This new Khoros forum is still a work in progress.  Community Feedback is the new place to post forum feature requests and bug reports.  

Melissa Rios posted a summary of updates from Oct 18th.  Marking correct answers didn't make the list this time around.

https://community.adobe.com/t5/Community-Feedback/October-18th-Release-Notes/td-p/10678796

[Jon Fritz]

Notepad++ also works well when DW chokes on any given code.