Hello,

I noticed that a lot of work has been done on the menu class. The problem which appeared a few weeks ago seems to have been solved.

But today I noticed a new problem :

A customer of mine has still 2 PC running on Windows XP. On these PC's, the different menues are placed on top of each other. They are not readable. They are absolutely not useable.

I don't have Windows XP anymore so I can't give you an example. I just use the standard menu class which was provided in the FWH 15.09.

Anyone any idea what's wrong?

Shouldn't there be a backwards compatibility?

Thanks a lot in advance.

Michel,

We are going to check it on XP again.

Could you get a screenshot ? thanks

karinha wrote:look please.

http://forums.fivetechsupport.com/viewtopic.php?f=16&t=31378&start=15

Regards,

Michel

Problem solved?

Cristobal,

It seems that the problem has been solved.

Thanks a lot for your help.

Cristobal,

great work!

many thanks

Hi,
could you please share the solution (eg. an updated tmenu class) ?
I still have problem with the menu with a FWH app in a cloud environment.
Thank you

Marco,

We are going to publish a new FWH 15.09 build 4, we need a couple of days.

In the meantime, if you are in a hurry, we can email you the FWH libs to solve the menu issues

Hi,
I don't know if the menu problem on XP is solved,
anyway on my app the problem is still there
It seems a refresh problem.

http://www.softwarexp.co.uk/beta/test/test.html

Marco,

Are you already using FWH 15.09 build 4 ?

Yes, I'm testing with build 4. I'm running the app in a VM machine on cloud environment.
The menus were fine with FWH Dec 2012

See this video showing the problem http://www.softwarexp.co.uk/beta/test/test.html

To access go to

www.condominio.biz
user: testca
pwd: A12345678

Source code:
// Some PullDown menu samples

include "FIVEWIN.CH"

static oWnd

//------------------------------------------------------------//

FUNCTION Main()

DEFINE WINDOW oWnd ;
TITLE "Testing PullDown Menus" ;
MENU BuildMenu()

ACTIVATE WINDOW oWnd

RETURN NIL

//------------------------------------------------------------//

FUNCTION BuildMenu()

local oMenu, oMenu1, oMenu2
local oSub1,oSub2,oSub3
MENU oMenu
MENUITEM "Test 1"
MENU
MENUITEM "Item 1"
MENUITEM "Item 2"
ENDMENU
MENUITEM "Test 2"
MENU
MENUITEM "Item 1"
MENUITEM "Item 2"
ENDMENU
MENUITEM "Test 3"
MENU
MENUITEM "Item 1"
MENUITEM "Item 2"
ENDMENU
MENUITEM "Test 4"
MENU
MENUITEM "Item 1"
MENUITEM "Item 2"
ENDMENU
ENDMENU
// oMenu2:Disable()
RETURN (oMenu)

I noticed the same problem, but .... it doesn't happen on every PC. On some it does, on other it doesn't.

Very strange.

It seems like a refresh() problem.