Skip to main content
N
Noquarter76
Participating Frequently
January 27, 2017
Question

Typing classes and bugs

  • January 27, 2017
  • 3 replies
  • 454 views

In the last version of Dreamweaver, when typed a full class name and hit ENTER it would put the curser after the ".  Similar to how if you hit enter after partially typing.  In this version it now line breaks when you finish typing and click enter.   Worst when you do an undo it deletes the entire line....   This is driving me nuts.  There is no reason to line break inside class "".  Is this a setting or just a bug?

Also, live view does not like to update when I compile less files outside of dreamweaver.

Thanks,

    This topic has been closed for replies.

    3 replies

    N
    Noquarter76Author
    Participating Frequently
    January 27, 2017

    Is there a way to get my old Dreamweaver back for now?

    Preran
    Preran
    Legend
    January 27, 2017

    Yes of course. Use this link. Download and install Creative Cloud apps

    Nancy OShea
    Community Expert
    Nancy OSheaCommunity Expert
    Community Expert
    January 27, 2017

    Can I ask why you compile LESS files outside DW?

    The latest DW supports this you know.

    Nancy

    Nancy O'Shea— Product User & Community Expert
    N
    Noquarter76Author
    Participating Frequently
    January 27, 2017

    Because I am time crunched right now and have not had a chance to look into the less editor in DW.  I have been using the same LESS editor for a long time and am familiar with it so I just use it still for the time being.

    pziecina
    pziecina
    Legend
    January 27, 2017

    Dreamweaver now places the cursor between the 2 "". So there is no requirement to hit enter.

    A number of users have complained about this, (myself included) and submitted it as a bug. I don't think there are any current plans to change this behaviour though.

    N
    Noquarter76Author
    Participating Frequently
    January 27, 2017

    "Dreamweaver now places the cursor between the 2 "". So there is no requirement to hit enter."

    This is not the issue.  The issue comes once you are already inside the ""

    generally you type class=  <ENTER>

    Dreamweaver puts the cursor between the ""

    -------------------------------------------------------------------  Still doing these steps as it should

    Then you type half a class, it pops in the drop down and you click enter or click it with mouse.

    Dremweaver fills it out and then keeps the cursor inside the quotes ready to write another class

    ------------------------------------------------------------------  Still doing this as it should

    The change comes when you type a full class without hitting enter.

    Previously, if you typed a full class and hit <ENTER> DW would put the cursor outside of the last "  thinking that you are ready to end the HTML > or move on to id, etc.

    -------------------------------------------------------------------  No longer does this.  It now line breaks

    In the context of writing classes there is NO reason to line brake.  Why would they make this change?  I have been writing code in DW since Macromedia days.  Why do they condition us and then change it willy nilly.  Ux teaches us we never make system changes unless we can improve the efficiency... this certainly does not do that.

    pziecina
    pziecina
    Legend
    January 27, 2017

    Noquarter76 wrote:

    In the context of writing classes there is NO reason to line brake. Why would they make this change? I have been writing code in DW since Macromedia days. Why do they condition us and then change it willy nilly. Ux teaches us we never make system changes unless we can improve the efficiency... this certainly does not do that.

    The code editor now uses the Brackets code editor, which has completely different behaviour, (as you have found).

    Some of the changes are welcome, most are not, and I have yet to find anyone who is more than 60% satisfied with the changes made. I think they forgot that one expects changes of behaviour when using a different code editor, especially when that code editor is free, as Brackets is, but not when the code editor is in an established program, and especially when one is paying for that program.

    All I can suggest is that you post a feature request to the revert back to the old behaviours at -

    https://dreamweaver.uservoice.com/

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices