Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Development
  3. [2.1 Beta] Program 'chapter' order changed since 2.0

[2.1 Beta] Program 'chapter' order changed since 2.0

Scheduled Pinned Locked Moved Development
4 Posts 2 Posters 1.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.
  • D Offline
    D Offline
    DavidZH
    wrote on last edited by
    #1

    Not sure if this is in the right category:

    Yesterday I changed my library to the latest Github Beta and the sketch I am finalising now ran in a different order!
    Previously, the "setup" runs before "presentation". In 2.1 its the other way round! It's not a big problem for me, I can program around that with a "before" function, but a lot of people could be very confused.

    In my setup the sketch reads some defines to find out what sensor to present, so that's why it matters for me here.

    Was this intended behaviour? Or a little oversight?

    Keep up the good work!

    mfalkviddM 1 Reply Last reply
    0
    • D DavidZH

      Not sure if this is in the right category:

      Yesterday I changed my library to the latest Github Beta and the sketch I am finalising now ran in a different order!
      Previously, the "setup" runs before "presentation". In 2.1 its the other way round! It's not a big problem for me, I can program around that with a "before" function, but a lot of people could be very confused.

      In my setup the sketch reads some defines to find out what sensor to present, so that's why it matters for me here.

      Was this intended behaviour? Or a little oversight?

      Keep up the good work!

      mfalkviddM Offline
      mfalkviddM Offline
      mfalkvidd
      Mod
      wrote on last edited by
      #2

      @DavidZH looks like an intentional change, see https://github.com/mysensors/MySensors/pull/513 for details.

      D 1 Reply Last reply
      1
      • mfalkviddM mfalkvidd

        @DavidZH looks like an intentional change, see https://github.com/mysensors/MySensors/pull/513 for details.

        D Offline
        D Offline
        DavidZH
        wrote on last edited by
        #3

        @mfalkvidd

        Thanks! I should check Github moe often I guess. 😁

        mfalkviddM 1 Reply Last reply
        2
        • D DavidZH

          @mfalkvidd

          Thanks! I should check Github moe often I guess. 😁

          mfalkviddM Offline
          mfalkviddM Offline
          mfalkvidd
          Mod
          wrote on last edited by
          #4

          @DavidZH you're welcome. No worries, everyone can't keep track of everything :)

          1 Reply Last reply
          2
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          13

          Online

          11.7k

          Users

          11.2k

          Topics

          113.1k

          Posts


          Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • MySensors
          • OpenHardware.io
          • Categories
          • Recent
          • Tags
          • Popular