next »

[David H.]

Hi all,

As more of our clients switch to Genero V2+ we are getting reports of (and on occasions noticing ourselves) an annoying intermittent problem which has proven difficult to track down so far, so I'd thought I'd see if anybody on the forum has any suggestions. We have a popup menu which uses the following style:-

 

Code

 <Style name="Window.SimpleMenu">
    <StyleAttribute name="windowType" value="modal"/>
    <StyleAttribute name="border" value="normal"/>
    <StyleAttribute name="sizable" value="no"/>
    <StyleAttribute name="actionPanelPosition" value="none"/>
    <StyleAttribute name="ringMenuPosition" value="none"/>
    <StyleAttribute name="defaultStatusBar" value="1"/>
    <StyleAttribute name="windowOptionClose" value="yes"/>
    <StyleAttribute name="statusBarType" value="none" />
    <StyleAttribute name="windowState" value="normal" />
    <StyleAttribute name="position" value="center" />
    <StyleAttribute name="startMenuPosition" value="poptree" />
    <StyleAttribute name="startMenuShortcut" value="control-shift-L" />
    <StyleAttribute name="startMenuSize" value="small" />
  </Style>

Normally menu's of this style appear correctly. However every so often (sometimes days, other times just minutes) the window gets resized and we have been unable to find what causes this.  I'm attaching a couple of screen shots to show what happens. Since the window is not resizable I'm at a loss to explain what could cause its stored off sizing to change every so often. FYI we've never seen this happen with v1.3x either...

Any thoughts/suggestions would be most welcome.

David

[Reuben B.]

David,

You mention that the window shouldn't be resizable, did you consider adding the following styleattribute.  This should at least stop the annoying intermittent problem occuring.

<StyleAttribute name="forceDefaultSettings" value="1" />


One possibility for the problem occuring although it is unlikely as I would expect it to occur with 1.3 as well, but I'll mention it as you may have made a change to your app between 1.3 and 2 (and it is interesting) is that you have a window and/or form with the same name used elsewhere in your application.  The stored settings are saved away in the registry by window name (for x,y, state), and by form name (for height,width) so if you have 2 or more instances using the same window name and/or 2 or more instances using the same form name then the settings will be shared between the 2 or more windows and/or forms.

Run this code and you'll hopefully see that if you reposition and move the first window that appears, that these stored settings are then applied to the second window as it shares the same name even though its contents maybe completely different

Code

MAIN
   OPEN WINDOW w1 WITH FORM "dir1/form"
   MENU ""
      ON ACTION accept
         EXIT MENU
   END MENU
   CLOSE WINDOW w1
 
   OPEN WINDOW w1 WITH FORM "dir2/form"
   MENU ""
      ON ACTION accept
         EXIT MENU
   END MENU
   CLOSE WINDOW w1
END MAIN

If the problem continues, keep an eye on the values in the registry.  One issue a few years ago was reported as a column width suddenly being too small, when in actual fact the column width was decrementing by 2 pixels each time the window was opened but of course it was only reported once it got too small.   I'd also be curious to see the .per.

Reuben

PS You describe it as a popup menu, it looks like more like a DISPLAY ARRAY to me.  Did you consider a MENU STYLE="popup" for what I am guessing is a library function? 

[David H.]

Hi Reuben.

Thanks for responding. Yes I was aware of forceDefaultSettings but have not used it yet as I wanted to a) isolate the cause of the issue and b) let users control the position where the window is opened. I may however be forced to adopt this as its definitely the lesser of two evils..!

I'm also confident that both the window (menu_w) and form (menu14s) are only used in 1 function in the application, so we don't have more than one instance affecting another...

I will have a go at trying to monitor the registry using Regmon. The problem is that the error can occur very infrequently and try as we might nobody has yet managed to come up with steps to reproduce the problem. It definitely does not occur with Genero v1.32x though...

I'm am attaching the PER file to satisfy your curiosity :-)

Kind regards,

David

p.s. I don't think I've ever played with a "popup" menu before. You are right the implementation of this context sensitive menu is indeed using a data driven DISPLAY ARRAY statement. In fact all our menu's are implemented by DISPLAY ARRAY's...

p.p.s. How I enjoyed retyping this message when the previous version got wiped out by the forum software when I forgot to zip the attachment and clicked post...