Delay differences depending on view

Last post 08-27-2007, 1:54 PM by lue. 10 replies.
Sort Posts: Previous Next
  •  08-21-2007, 6:51 PM 32697

    Delay differences depending on view

    Adam,
     
    Our users are very frustrated with this problem and our tech support people are inundated with complaints. Please don't suggest we use another editor or go back to a buggy previous version. We have paid you for this one and have invested a lot of time building a user framework around it. So we need to work with what we have.
     
    What we want is simply to have an editor that our users can work with and that acts like any other text editor. From a user's viewpoint, they don't care about underlying technical issues -- they just want the product to work.
     
    BTW, this Cutesoft ID (fredd) is used by all 3 of our support personnel. Some are more annoyed than others because they are frustrated with user complaints so sometimes their comments are a bit abrupt...
     
    Doesn't make sense:
     
    One of the biggest issues we have is that it makes no sense that we can type without any delays when there are only a few words in the content, but when there are thousands of words, each keystroke doesn't display at the same rate. Something is very out of whack here. It doesn't matter if we are typing at the beginning or end of a long document, the delay is the same. Is your code checking through the entire document on every keystroke? Why would this delay occur?
     
    Identifying the delay:
     
    When I load up the editor with 1000 lines of typing and type in normal view, the delay is very significant.
     
    If I then switch to HTML view and type something, the editor still exhibits delays but the delay is quite a bit less than in the Normal view. There is still an annoying delay but because the HTML view is active I would think there should be no delay at all, assuming you are not monitoring key events in that mode...
     
    Are you monitoring the key events even when CE is in the HTML view? If not, then why would there still be a delay in that mode?
     
    I think if you can identify the reason for the delay when in the HTML view and eliminate it, it will help significantly to reduce the typing display delay in Normal view.
     
    Another possibility: you have multi-undo levels built in so that must be taking some time each time a key is pressed. Could this be contributing to the delay?
     
    And by the way, when I set EnableClientScript to false, there is no delay even when there is ten times as much content, so the problem definitely is in the interaction with script somewhere.
     
    Thanks, Adam
    FredD
     
     
     
  •  08-23-2007, 4:14 AM 32747 in reply to 32697

    Re: Delay differences depending on view

    We have the same problem and we spended a lot of time to find a way for better performance. We hope that cutesoft has a solution (our money they have ...). We tested today the fck-editor. This editor has no delay problem if we work with longer textes.

    chris

  •  08-23-2007, 9:54 AM 32761 in reply to 32697

    Re: Delay differences depending on view

    In Cute Editor, we parse the HTML code in the realtime and clean it automatically.
     
    Please try the following suggestions for the time being. I will find out more options while working with the developers.
     
    1. Set ShowTagSelector property to false
     
     
    2. Set ConvertHTMLTagstoLowercase property to false.
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  08-23-2007, 10:41 AM 32766 in reply to 32697

    Re: Delay differences depending on view

    fredd:
    Adam,
     
    Our users are very frustrated with this problem and our tech support people are inundated with complaints. Please don't suggest we use another editor or go back to a buggy previous version. We have paid you for this one and have invested a lot of time building a user framework around it. So we need to work with what we have.
     
    What we want is simply to have an editor that our users can work with and that acts like any other text editor. From a user's viewpoint, they don't care about underlying technical issues -- they just want the product to work.
     
    BTW, this Cutesoft ID (fredd) is used by all 3 of our support personnel. Some are more annoyed than others because they are frustrated with user complaints so sometimes their comments are a bit abrupt...
     
    Doesn't make sense:
     
    One of the biggest issues we have is that it makes no sense that we can type without any delays when there are only a few words in the content, but when there are thousands of words, each keystroke doesn't display at the same rate. Something is very out of whack here. It doesn't matter if we are typing at the beginning or end of a long document, the delay is the same. Is your code checking through the entire document on every keystroke? Why would this delay occur?
     
    Identifying the delay:
     
    When I load up the editor with 1000 lines of typing and type in normal view, the delay is very significant.
     
    If I then switch to HTML view and type something, the editor still exhibits delays but the delay is quite a bit less than in the Normal view. There is still an annoying delay but because the HTML view is active I would think there should be no delay at all, assuming you are not monitoring key events in that mode...
     
    Are you monitoring the key events even when CE is in the HTML view? If not, then why would there still be a delay in that mode?
     
    I think if you can identify the reason for the delay when in the HTML view and eliminate it, it will help significantly to reduce the typing display delay in Normal view.
     
    Another possibility: you have multi-undo levels built in so that must be taking some time each time a key is pressed. Could this be contributing to the delay?
     
    And by the way, when I set EnableClientScript to false, there is no delay even when there is ten times as much content, so the problem definitely is in the interaction with script somewhere.
     
    Thanks, Adam
    FredD
     
     
     
     
    fredd,
     
    Try this example now:
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  08-23-2007, 1:24 PM 32781 in reply to 32766

    Re: Delay differences depending on view

    It's much better now. Thank you, but I wish we didn't have to push and complain so much to get these things done.
     
    It would be much more courteous if you would simply answer the messages with something like "let me check that" instead of just ignoring the messages.
  •  08-23-2007, 1:41 PM 32785 in reply to 32781

    Re: Delay differences depending on view

    fredd,
     
    >>but I wish we didn't have to push and complain so much to get these things done.
     
    We have to get all brains together to dicusss/resolve this.
     
    Please download the control again. And update all the client files under Editor/Scripts folder.
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  08-23-2007, 1:55 PM 32787 in reply to 32785

    Re: Delay differences depending on view

    Again, by simply adding a message stating you are working on the issue would go a long way to preventing frustrated customers. Like I said, our tech support are inundated with user complaints about this issue (and a few others). I can't tell them anything because you don't tell me anything about your progress with the issue.
     
    So my people get angrier and angrier. A quick update is all we need from you so that I can tell our people that the problem is being worked on. In turn, they can tell the users.
     
     
  •  08-23-2007, 1:57 PM 32789 in reply to 32785

    Re: Delay differences depending on view

    >>Please download the control again. And update all the client files under Editor/Scripts folder.<<
     
    The download is dated August 15, 2007 so I assume it's not the current release.
  •  08-23-2007, 2:53 PM 32800 in reply to 32789

    Re: Delay differences depending on view

  •  08-23-2007, 5:35 PM 32819 in reply to 32800

    Re: Delay differences depending on view

    I've downloaded and implemented the August 23 download, but for some reason, the problem is still there. The DLL is dated August 14 2007. Is that correct? I see a couple of the .js files have been updated.
     
    Any ideas on this?
  •  08-27-2007, 1:54 PM 32950 in reply to 32819

    Re: Delay differences depending on view

    In mostly cases the delay differences are solved in the last version - thanks!. But try to edit this or other tables (copied from a doc-file or not ...): Edit a cell and than go to another cell. Massive typing delays are the result.

    Chris

    Je Seite zu testen:

    ·         Öffnen (view, edit)

    ·         Erfassen (Neuanlage)

    ·         Ändern

    ·         Speichern

    ·         Selektieren (Listen)

    ·         Sortieren (Listen)

    Grün = getestet, okay

    Rot = getestet, nicht okay bzw. Änderungsvorschlag

    Blau = Test aufgeschoben

    ??? = Kein Test bzw. Seite nicht gefunden

    Nr.

    betrifft

    Funktion

    Ergebnis

    F/C/I

    Priorität 0-5

    Wer?

    Erledigt %

    Anm.


    Chart_MV









    Classification_LE









    Classification_LP









    Connector_LE









    Connector_LP









    Country_LP









    Default






    ???



    Diagram_LE









    DiagramForm_LP









    DiagramType_LE









    DiagramwithElement_LE









    DiagramwithElement_ME


    Status wird nicht gespeichert

    F

    4

    CL




    DiaItemDesign_LE


    ölölööüüüüüüü






    DotNet_LE


    pppppppp






    Element_Admin


    ok







    Element_GV









    Element_LN


    Falsches Symbol für „Neuen Datensatz einfügen“ ( statt )

    F

    2

    CL




    Element_LP


    Sollte nicht auch der EleType zu selektieren sein (z. B. für das HPM)?

    C

    2

    CL




    Element_LS


    ok







    Element_LV_basis






    ???



    Element_ME


    ok







    Element_ME_small


    ok







    Element_MV


    Konfig: Upload im Basis-Panel, Hyperlink im Detail?

    C

    2

    CL/AS




    Element_MV_small


    Konfig: Wäre nicht der Langtext im „-“-Panel sinnvoll? So enthält die geöffnete Small-Seite kaum mehr Info als der Grid

    C

    2

    CL/AS




    Element_RT









    Element_Tree









    ElementAdress_LP


    ok







    ElementCalc_LV









    ElementCalcRule_MV









    ElementClass_LE









    ElementCopy_ME






    ???



    ElementData_LE









    ElementDataFieldSelect_LP









    ElementDataSheet_LS









    ElementDataSheet_ME









    ElementFavorit_LP


    Ein „<“ im Notizfeld bringt einen Serverfehler

    F

    4

    CL




    ElementFieldSelect_LP









    ElementGridSelect_LP


    ok







    ElementParameter_LP









    ElementRating_LV









    ElementRatingList_LV









    ElementRating_ME


    Ein „>“ im Kommentarfeld ergibt Serverfehler







    ElementRecOrg_LV









    ElementRecOrgAllowed_LV


    Selektion nach Element-Typ funktioniert nicht

    F

    3

    CL




    ElementReport_LV









    ElementReportRef_LV


    Verweise werden mehrfach angedruckt (z. B. BD6010, EleID 67: vier Mal)

    F

    4

    CL




    ElementToElement_LP









    ElementToElement_MP


    ok







    ElementToElement_MV


    ok







    ElementToElementParameter_LP









    ElementType_LE









    ElementTypeDiagram_LE









    ElementTypeDiagram_LP









    ElementTypeDiagramSelect_LP









    ElementTypeGridSelect_LP









    ElementUser_LE









    ElementUser_LP









    ElementUserPerson_MV









    ElementUserRecOrg_LV


    Selektion nach Usern geht nicht

    F

    3

    CL




    ElementUserSelfService_ME









    Footer






    ???



    FooterSmall






    ???



    Header






    ???



    HeadPage






    ???



    History_LP


    Generell: In der EleType-Auswahl zur Selektion in der History-Liste ist die Auswahl von Ele-Typen möglich, auf die der User gar keinen Zugriff hat (MaxKonf.)

    F

    4

    CL




    ImageGen






    ???



    Login









    MainPage









    MainPage_MV









    MyObjectPage_LP









    MyOrgPage_LP


    Name der Org.-Einheit fehlt in der Ergebnisliste

    F

    4

    CL




    MyOwnerPage_LP


    Generell: In der EleType-Auswahl zur Selektion in der History-Liste ist die Auswahl von Ele-Typen möglich, auf die der User gar keinen Zugriff hat (MaxKonf.)

    F

    4

    CL




    MyPage_LP






    ???



    MyPropage_LP









    NavPage


    ok







    PageDataError






    ???



    PageNotAllowed






    ???



    PageNotAllowedMode






    ???



    PageNotAllowedWrite






    ???



    PromolCHangeLog_LE






    ???



    RecDel_LP


    ok







    RecMenu_LE









    RecMenu_LN









    RecMenuCheck_LV









    RecParameter_LE









    RecPriority_LP


    ok







    RecPub_LP


    ok







    RecRating_LE









    RecRating_LP









    RecScale_LE









    RecStatus_LP


    ok







    RecVerLevel_LP


    ok







    RecVis_LP


    ok







    RecWorkFlow_ME


    Prüfen: Ablehnung der Freigabe (mit verteilten Usern)









    Liste wird länger, wenn man öfter auf „Suchen“ klickt, URL-Paramater geht verloren









    Generell: In der EleType-Auswahl zur Selektion in der History-Liste ist die Auswahl von Ele-Typen möglich, auf die der User gar keinen Zugriff hat (MaxKonf.)







    SysHelpPage_LE


    fffffffflllllllllffffff4wet34t35t45






    SysHelpVariable_LE

    fwegferggg
    llll






    SysHelpVarType_LE


    lllllllllllll






    test






    ???



    Usergroup_LE









    Usergroup_LP









View as RSS news feed in XML