screen showing broken in AppWizard 1.32_6.28 vs 1.08_6.14d

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • screen showing broken in AppWizard 1.32_6.28 vs 1.08_6.14d

      Attached is a sample project with 3 screens:
      1. first one (screen_00) has a button which opens screen_01
      2. screen_01 should show screen_02 on top of it
      3. in the end it should be shown screen_01 with screen_02 together:
        1. this works as expected with AppWizard 1.08_6.14d
        2. but with newer AppWizard 1.32_6.28 screen_01 closes and instead screen_00 plus screen_02 are shown!
      Is this a known bug? Any workarounds to get the expected behaviour with the new AppWizard?
      Thanks,
      Daniel
      Files

    • Tested with latest AppWizardTrial_V136c_632c and unfortunately the misbehaviour is still there. The screens are modified now so that they are not fully overlapping in order to see better the mis/behaviour (that the screen_01 is not shown with latest AppWizard):
      Files

      • test2.zip

        (990 Byte, downloaded 400 times, last: )

    • Hi Daniel,

      Before the last release screens could be of any size and have any position. But this was a design flaw and could sometimes lead to unwanted behavior.
      With the latest version screens are always at the position (0,0) and have the display size that is set in the BSP.

      So the behavior that you described is correct: On the button press SCREEN_01 is shown which shows SCREEN_02 on INITDIALOG. So in the end SCREEN_02 is on top of all other screens. And as said, all screens now have the size of the display. That is why the SCREEN_01 below is not visible.

      To achieve the same behavior as before, you would have to use a window instead of a screen here. The window also acts as a container for widgets (like the screen), but can have an arbitrary size and position.
      So SCREEN_02 would have to be replaced by a window that is a child of SCREEN_01. I have modified your project, just have a look.

      I hope this helps.

      Best regards,
      Florian
      Files

      • test1.zip

        (1.06 kB, downloaded 425 times, last: )
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Thank you Florian for the fast answer: yes, the modified project works as expected, so that seems to be a good workaround!
      It's still not clear why in the modified test2 we can still end-up having 2 "screens" displayed simultaneously (screen_00 and screen02 in that example) both screens being active (not just drawn, because I can still click on the button from original screen_00):

      Is there some rationale for still having multiple simultaneous screens and is this something which is going to be changed too?
      Thank you,
      Daniel

    • Hi Daniel,

      Did you reproduce this with the project I sent you? In that project there is no SCREEN_02 anymore, instead it is a window. That window is a child of SCREEN_01, so it should only be visible when that screen is shown.

      Best regards,
      Florian
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hi Florian,
      the last question addressed the "test2.zip" project from my second post of this thread, because that doesn't quite follow your "with the latest version screens are always at the position (0,0) and have the display size that is set in the BSP" explanation.
      In that "test2.zip" project the screens were defined in AppWizard intentionally with a position different from (0,0) and a size smaller than BSP and the result is that only 2 screens (screen_00 and screen_02) are shown but not screen_01: what is then the logic here? If it's described in the manual, can someone please point to the chapter which specify which screens are automatically closed and which not?
      In the AppWizard manual there is a reference to "stay on top" / "persistent mode" property as "makes sure a screen is displayed on top of all other screens", but in that "test2.zip" there are no such settings, so:
      • when screen_02 is opened, why the screen_00 is also not closed? why only screen_01 is closed?
      • Is it because screen_02 overlaps partially with screen_01 but not with screen_00? Is this intentional and described somewhere: if not, can it be clarified please?


      Thank you,
      Daniel