Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. [SOLVED]Undocumented features
Forum Updated to NodeBB v4.3 + New Features

[SOLVED]Undocumented features

Scheduled Pinned Locked Moved QML and Qt Quick
10 Posts 5 Posters 4.2k 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.
  • I Offline
    I Offline
    ixSci
    wrote on last edited by
    #1

    Hi folks!

    I've just stumbled on some undocumented signal: onCursorRectangleChanged
    This signal is used in the example of scrolling in the QML TextEdit element documentation section. But there are no mentions about the signal anywhere. And now I'm curious how many features QtQuick has which documentation knows nothing about? And how can I discover them?

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

      bq. And how can I discover them?

      you will be surprised, but ... everything is in the SOURCES

      1 Reply Last reply
      0
      • I Offline
        I Offline
        ixSci
        wrote on last edited by
        #3

        Kxyu, can you point where QML sources are located? I've found nothing.

        1 Reply Last reply
        0
        • M Offline
          M Offline
          mohsen
          wrote on last edited by
          #4

          I couldn't understand! do you need to learn about signals and slots?

          1 Reply Last reply
          0
          • I Offline
            I Offline
            ixSci
            wrote on last edited by
            #5

            No, I want to know what signals can be emitted by a particular element, what methods and properties it has. I've experienced some troubles with attempt to locate onCursorRectangleChanged documentation. Why shouldn't I think there are another undocumented signals or methods or even properties in QML?

            1 Reply Last reply
            0
            • K Offline
              K Offline
              kamalakshantv
              wrote on last edited by
              #6

              Some of these features might be kept for testing. I remember something similar being discussed somewhere. Also one cannot rely completely on undocumented API's as they might be removed in future versions.

              1 Reply Last reply
              0
              • I Offline
                I Offline
                ixSci
                wrote on last edited by
                #7

                Sure you are right. But this signal is used in the example provided by Trolls and I have a solid feel that it won't be thrown away in the future release. Also I use it for scrolling purpose but I'm not sure that I fully understand the signal meaning. And it is not so good feeling when you have a little control over the code...
                That is my point: if it can be retrieved by the public interface it should be documented.

                1 Reply Last reply
                0
                • K Offline
                  K Offline
                  kamalakshantv
                  wrote on last edited by
                  #8

                  [quote author="ixSci" date="1294083775"]
                  That is my point: if it can be retrieved by the public interface it should be documented. [/quote]

                  Yes, I agree with this.

                  1 Reply Last reply
                  0
                  • M Offline
                    M Offline
                    mbrasser
                    wrote on last edited by
                    #9

                    [quote author="ixSci" date="1294075256"]Hi folks!

                    I've just stumbled on some undocumented signal: onCursorRectangleChanged
                    This signal is used in the example of scrolling in the QML TextEdit element documentation section. But there are no mentions about the signal anywhere. And now I'm curious how many features QtQuick has which documentation knows nothing about? And how can I discover them?[/quote]

                    Hi,

                    All properties in QML automatically have an associated on<PropertyName>Changed signal handler available from QML. These aren't individually documented, but http://doc.qt.nokia.com/4.7-snapshot/qml-extending-types.html#property-change-signals provides a brief description of the concept. It should probably be added to the language introduction as well, as the feature isn't specific to properties added from QML.

                    Regards,
                    Michael

                    1 Reply Last reply
                    0
                    • I Offline
                      I Offline
                      ixSci
                      wrote on last edited by
                      #10

                      Thanks Michael! Good link with a good explanation.

                      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