Dreamveaver CC 2017.0.1 - Problem with Live View update

[komhit]

It is something that is not as it was. When I do something in CSS Design panel, nothing happens in LiveView. If I use reload nothing happens. I must save stylesheet before using realod.

When I use Inserter panel to enter the Bootstrap elements must I often click on the elements two or three times before anything happens.

The first version of 2017, I had trouble as written here, but it was fixed in a small upgrade. Then came 2017.0.1 who set Dreamweaver back in.

If there are problems between MacOS 10.12.2 and Dreamweaver I do not know, but I work with many people who have the same problem.

Anyone know if there's something new about how to resolve this issue, or whether Adobe aware of the problem and resolve it? Appreciate answer when this starts to get frustrating. Like Live View, when it works. Nice to tweak elements.

[pziecina]

Not 100% certain if this is the answer, but I can see why this would happen in Dw 2017.

Dw 2017 now has built-in file recovery, in order for this to work correctly the file should be saved often. As most crashes or freezes are caused by the switching of views, then asking for someone to save the file before Dw does so, would I think be a logical consequence of adding this feature.

[komhit]

Thank pziecina.

As you type, this may seem logical. But I would like to then be able to turn off the built-in file recovery. I often use Live View in combination with Split View for fine tuning. I have not experienced program crash in this context as far as I remember. I'll see if Adobe or anyone else gets involved with some suggestions on how this can be resolved. As it is now, I have no particular pleasure from Live View or Live Preview in Browser although I have two monitors.

[pziecina]

I suppose an auto-save feature may help, but I can then imagine that users would complain when they create a new page and get the 'save as' prompt.

[komhit · Accepted solution]

Today I upgraded MacOS Sierra to version 10.12.3 and probelem was resolved. Things are working properly so far. So I apologize to Adobe for having believed the problem lay with them this time. This time it was Sierra 😞 obviously.