Bug? Different execution cycle between Debug mode and Release

Discussion in 'Bugs & wishlist' started by HammerZeta, Jul 1, 2018.

  1. HammerZeta

    HammerZeta New Member Licensed User

    Hello

    I'm doing a library that creates a dialog to select a file.

    The library contains a Class and an Activity. The Class is used to configure the dialog and to call the InitializeDialog subroutine of the Activity using CallSubDelayed3.

    When I run the program in debug and release mode, the Activity does not follow the same life cycle when called by the CallSubDelayed3.

    In Debug mode it executes the Activity_Create, the InitializeDialog subroutine (called by the CallSubDelayed3) and finally the Activity_Resume.

    While in Release mode it executes the Activity_Create, the Activity_Resume and finally the InitializeDialog subroutine (called by the CallSubDelayed3).



    When I run in debug mode:

    ** Activity (filedialog_activity) Create, isFirst = true **
    sending message to waiting queue (CallSubDelayed - InitializeDialog)
    running waiting messages (1)
    << EXECUTE InitializeDialog !! >>
    ** Activity (filedialog_activity) Resume **


    When I run in release mode:

    ** Activity (filedialog_activity) Create, isFirst = true **
    ** Activity (filedialog_activity) Resume **
    << EXECUTE InitializeDialog !! >>


    Is it a B4A bug?

    A greeting.
     
  2. Erel

    Erel Administrator Staff Member Licensed User

    Are you testing it with the source code or the compiled library?

    As a general rule it is not advised to create activities in libraries. It will be more flexible if you implement it as a custom dialog instead.
     
  3. HammerZeta

    HammerZeta New Member Licensed User

    I'm doing some tests, I'll tell you more details in a few days. Lately I have little free time.

    Thank you
     
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice