Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Behind the Scenes
  3. Qt.io webservices
  4. [solved] New documentation format usability issues
Forum Updated to NodeBB v4.3 + New Features

[solved] New documentation format usability issues

Scheduled Pinned Locked Moved Qt.io webservices
7 Posts 5 Posters 3.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    fbolduc
    wrote on last edited by
    #1

    There are usability problems with the new documentation.

    I'm taking QPlainTextWidget to illustrate them.
    See: http://developer.qt.nokia.com/doc/qt-4.8/qplaintextedit.html

    First problem: there are missing public functions

    "setLineWrapMode ( LineWrapMode mode )" is a public function, yet it is not listed in the "Public Functions" section. It is listed elsewhere. It should be in the "Public Functions" section.

    Second problem: enum function arguments are not linked to enum definitions.

    When I look at the documentation for "setLineWrapMode ( LineWrapMode mode )", I can't click on enum "LineWrapMode". I should be able to click on the enum argument and be directed to it's definition.

    1 Reply Last reply
    0
    • K Offline
      K Offline
      koahnig
      wrote on last edited by
      #2

      welcome to devnet

      Did you considerto file a bugreport on "JIRA":https://bugreports.qt.nokia.com/secure/Dashboard.jspa ?
      JIRA is the official tool for bug reports and ensures that someone will take of the issue.

      Vote the answer(s) that helped you to solve your issue(s)

      1 Reply Last reply
      0
      • G Offline
        G Offline
        goetz
        wrote on last edited by
        #3

        lineWrapMode is a property, and the setters and getters for properties are listed with those. It can be useful to have them listed in the methods list too.

        http://www.catb.org/~esr/faqs/smart-questions.html

        1 Reply Last reply
        0
        • F Offline
          F Offline
          fbolduc
          wrote on last edited by
          #4

          I created an issue in JIRA:

          https://bugreports.qt.nokia.com/browse/QTWEBSITE-348

          1 Reply Last reply
          0
          • M Offline
            M Offline
            mgran
            wrote on last edited by
            #5

            Thanks fbolduc :)

            Project Manager - Qt Development Frameworks

            1 Reply Last reply
            0
            • D Offline
              D Offline
              daviddoria
              wrote on last edited by
              #6

              It also seems you cannot see inherited signals. For example:
              http://developer.qt.nokia.com/doc/qt-4.8/QStringListModel.html

              shows no signals. Clicking "Inherits", it's parent class also has no signals. Not until you get to the next "Inherits" do you see the signals. This is quite confusing. Doxygen has a "Show all members" where you could see things like that - is there something like that in the new docs?

              1 Reply Last reply
              0
              • M Offline
                M Offline
                mgran
                wrote on last edited by
                #7

                We're quite close to getting the traditional layout online, had hoped for today even. So in a few business hours we hope this issue will have vanished into this air.

                Project Manager - Qt Development Frameworks

                1 Reply Last reply
                0

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved