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. QProcess documentation is inconsistent

QProcess documentation is inconsistent

Scheduled Pinned Locked Moved Qt.io webservices
documentationqprocessqtwebsite-648
11 Posts 4 Posters 3.4k Views
  • 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.
  • K Offline
    K Offline
    koahnig
    wrote on 25 Mar 2015, 16:58 last edited by koahnig
    #1

    The documentation of QProcess is insonsistent. I was searching for setting the environment in the method list at top and could not find anything. With Chrome search I could find a reference on page later. However, it is not marked as a proper reference.

    systemEnvironment can be found under static methods. There is a reference to setEnvironment, but it links to an obsolete page

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

    1 Reply Last reply
    0
    • C Offline
      C Offline
      Chris Kawa
      Lifetime Qt Champion
      wrote on 25 Mar 2015, 17:37 last edited by
      #2

      The docs are ok. setEnvironment is obsolete so it's not listed in the main doc page. The recommended method now is setProcessEnvironment and it is listed at the top as usual.

      K 1 Reply Last reply 25 Mar 2015, 17:59
      0
      • C Chris Kawa
        25 Mar 2015, 17:37

        The docs are ok. setEnvironment is obsolete so it's not listed in the main doc page. The recommended method now is setProcessEnvironment and it is listed at the top as usual.

        K Offline
        K Offline
        koahnig
        wrote on 25 Mar 2015, 17:59 last edited by
        #3

        @Chris-Kawa
        Sorry to disagree
        Certain processes need special environment settings in order to operate. You can set environment variables for your process by calling setEnvironment(). To set a working directory, call setWorkingDirectory(). By default, processes are run in the current working directory of the calling process.
        That is one section which still looks like that setEnvironment can be called (see on QProcess doc in section Communicating via channels 4th paragraph). Also later it is not clear. Only when using the link as mentioned in my initial post, you can see only indirectly through the page link shown by your browser. In the text itself it seems to be the original text. You need to scroll up to actually read that all those methods are obsolete.

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

        1 Reply Last reply
        1
        • C Offline
          C Offline
          Chris Kawa
          Lifetime Qt Champion
          wrote on 25 Mar 2015, 18:13 last edited by
          #4

          Ah, sorry. Yes, now I see it. Documentation bugs are reported just as any other via bug tracker.

          1 Reply Last reply
          0
          • K Offline
            K Offline
            koahnig
            wrote on 25 Mar 2015, 18:48 last edited by
            #5

            Filed a bug report on JIRA

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

            1 Reply Last reply
            1
            • C Offline
              C Offline
              Chris Kawa
              Lifetime Qt Champion
              wrote on 25 Mar 2015, 18:52 last edited by
              #6

              I see you filed it as a website bug. Documentation is part of the library and should be filed against the Qt library version you spotted it in, not the website, I think.

              1 Reply Last reply
              1
              • S Offline
                S Offline
                SGaist
                Lifetime Qt Champion
                wrote on 25 Mar 2015, 23:41 last edited by
                #7

                Hi,

                IIRC, the bug can be moved over by the admins so no need to duplicate it.

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                1
                • T Offline
                  T Offline
                  tekojo
                  wrote on 26 Mar 2015, 06:49 last edited by
                  #8

                  Moved to the "Qt" project and documentation in Bugtracker.
                  https://bugreports.qt.io/browse/QTBUG-45235

                  And thanks @SGaist for providing the patch, should I give the bug over to you actually?

                  1 Reply Last reply
                  0
                  • S Offline
                    S Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on 26 Mar 2015, 07:57 last edited by
                    #9

                    @tekojo You're welcome ! And yes :)

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    1 Reply Last reply
                    0
                    • K Offline
                      K Offline
                      koahnig
                      wrote on 26 Mar 2015, 08:37 last edited by
                      #10

                      Thanks guys for taking care

                      Where to file a bug report is not obvious when you are not on it on an everydays basis.

                      BTW I saw a couple of bug reports on my list which are no longer relevant with the move of the website. Those bugs are :
                      https://bugreports.qt.io/browse/QTWEBSITE-337
                      https://bugreports.qt.io/browse/QTWEBSITE-447
                      https://bugreports.qt.io/browse/QTWEBSITE-452
                      https://bugreports.qt.io/browse/QTWEBSITE-455
                      https://bugreports.qt.io/browse/QTWEBSITE-477

                      Since I am not able to close them, I left a message/comment for each report there as well.

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

                      T 1 Reply Last reply 26 Mar 2015, 08:57
                      1
                      • K koahnig
                        26 Mar 2015, 08:37

                        Thanks guys for taking care

                        Where to file a bug report is not obvious when you are not on it on an everydays basis.

                        BTW I saw a couple of bug reports on my list which are no longer relevant with the move of the website. Those bugs are :
                        https://bugreports.qt.io/browse/QTWEBSITE-337
                        https://bugreports.qt.io/browse/QTWEBSITE-447
                        https://bugreports.qt.io/browse/QTWEBSITE-452
                        https://bugreports.qt.io/browse/QTWEBSITE-455
                        https://bugreports.qt.io/browse/QTWEBSITE-477

                        Since I am not able to close them, I left a message/comment for each report there as well.

                        T Offline
                        T Offline
                        tekojo
                        wrote on 26 Mar 2015, 08:57 last edited by
                        #11

                        @koahnig thanks, closed those as requested.

                        1 Reply Last reply
                        0

                        8/11

                        26 Mar 2015, 06:49

                        • Login

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