Announcement

Collapse
No announcement yet.

[SOLVED] when change code in button , the app not come outdated

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • [SOLVED] when change code in button , the app not come outdated

    i have filmed a video to show you that i have to do other stuff to get the app get outdated to generate the new code

    http://youtu.be/Dfkn4h6PLJY

  • #2
    You can always generate code. Just select the application from your list of applications with the checkbox and choose the generate button on the bottom of the screen.

    Comment


    • #3
      Ok, the tab is not refreshed, but loaded from the browser cache. Does it do the same if you click on the icon or do a screen refresh?
      Albert Drent
      aducom software netherlands
      scriptcase partner, reseller, support and (turn-key) development
      www.scriptcase.eu / www.scriptcase.nl

      Comment


      • #4
        Hi tmleeek,

        I have performed a test on that case. The problem was reported for bugs team.

        For keep updated, please check the changelog of next releases.
        --
        Caio Guerra
        Scriptcase - Web Developer
        www.scriptcase.net

        Comment


        • #5
          Originally posted by c.vinicius View Post
          Hi tmleeek,

          I have performed a test on that case. The problem was reported for bugs team.

          For keep updated, please check the changelog of next releases.
          Maybe it would be a very good idea if you could assign a "bug number" to bugs like this.

          We have been told many times "Bug reported to development team" and then we hear nothing more for many months.
          It is hard to believe that the bug is really being tracked by anyone, if there is no number or other identifier assigned to it.

          For example of why NM has lost credibility, please read this thread: link
          Be sure to notice the dates on all of the posts in that thread.

          Dave
          Last edited by daveprue; 03-17-2015, 12:05 PM.
          Dave Prue
          Code Whisperer
          Lahar International Corp
          www.lahar.net

          Comment


          • #6
            Originally posted by daveprue View Post
            Maybe it would be a very good idea if you could assign a "bug number" to bugs like this.

            We have been told many times "Bug reported to development team" and then we hear nothing more for many months.
            It is hard to believe that the bug is really being tracked by anyone, if there is no number or other identifier assigned to it.

            Dave
            Scriptcase should implement an English bugtracker and assign a QC officer to control the process. The QCO should investigate the reported bug, check if it's not duplicate and then move the issue over to the Portuguese Mantis. Then the progress should be communicated through the En mantis. Looks a lot of work but: no more duplicate issues and investigations. No issues lost in the forum stream. And 'happy' customers as they can follow the progress. That's worth the effort.

            In addition to that, before release there should be a final test to confirm that the reported bugs are fixed and not new ones (re-)introduced.
            Albert Drent
            aducom software netherlands
            scriptcase partner, reseller, support and (turn-key) development
            www.scriptcase.eu / www.scriptcase.nl

            Comment


            • #7
              Originally posted by aducom View Post
              Scriptcase should implement an English bugtracker and assign a QC officer to control the process. The QCO should investigate the reported bug, check if it's not duplicate and then move the issue over to the Portuguese Mantis. Then the progress should be communicated through the En mantis. Looks a lot of work but: no more duplicate issues and investigations. No issues lost in the forum stream. And 'happy' customers as they can follow the progress. That's worth the effort.

              In addition to that, before release there should be a final test to confirm that the reported bugs are fixed and not new ones (re-)introduced.
              Albert,

              YOU ARE 100% CORRECT IN THIS POST

              Dave
              Dave Prue
              Code Whisperer
              Lahar International Corp
              www.lahar.net

              Comment

              Working...
              X