Announcement

Collapse
No announcement yet.

Suggest #year#

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Suggest #year#

    It would be nice to have a build-time constant #YEAR# so we could use it in Copyrights etc and not have to change it every year if an update is done.

  • #2
    Re: Suggest #year#

    Why not just set up #YEAR# yourself on the Design-time Constants tab?

    Then, you'd only have to change it in one place, once a year...and you could choose not to change it if for some reason you didn't want to.
    --[[ Indigo Rose Software Developer ]]

    Comment


    • #3
      Re: Suggest #year#

      I could set this myself (and am) but I'm looking at a whole bunch of different setups that I would have to do it to everytime. It's strictly to save me time in the long run.

      Comment


      • #4
        Re: Suggest #year#

        Understood. You can copy and paste constants between instances of SF6, though, so it might not be that hard to change, especially if you're using the same constants in all of your projects. (CTRL-A, CTRL-V, ALT-TAB, CTRL-V...sing it with me now! )

        Incidentally, if you use the Unattended Build (/B) option, you can pass design-time constants into SF6 via an INI file. This would let you use a single INI file to set all the constants that are common in your projects.
        --[[ Indigo Rose Software Developer ]]

        Comment


        • #5
          Re: Suggest #year#

          I can see where some built-in constants like #CURRENTYEAR#, #CURRENTMONTH#, etc. could be useful for copyright messages and as a mechanism to "time-stamp" your setup, etc. We will consider it for a future release. Thanks for the ideas! Keep them coming.

          - Brett

          Comment

          Working...
          X