FoxInCloud
menus
Gravatar is a globally recognized avatar based on your email address. menus
  Tuvia Vinitsky
  All
  Oct 19, 2014 @ 12:32pm
Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for exampme bars cannot have colors.

Gravatar is a globally recognized avatar based on your email address. Re: menus
  FoxInCloud Support - Thierry N.
  Tuvia Vinitsky
  Oct 20, 2014 @ 01:38am
1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.


-- thn (FoxInCloud)

Gravatar is a globally recognized avatar based on your email address. Re: menus
  Tuvia Vinitsky
  Thierry Nivelet (FoxInCloud)
  Oct 20, 2014 @ 06:08am

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.


Gravatar is a globally recognized avatar based on your email address. Re: menus
  FoxInCloud Support - Thierry N.
  Tuvia Vinitsky
  Oct 20, 2014 @ 06:44am
1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.




-- thn (FoxInCloud)

Gravatar is a globally recognized avatar based on your email address. Re: menus
  Tuvia Vinitsky
  Thierry Nivelet (FoxInCloud)
  Oct 20, 2014 @ 07:11am
Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.




Gravatar is a globally recognized avatar based on your email address. Re: menus
  FoxInCloud Support - Thierry N.
  Tuvia Vinitsky
  Oct 20, 2014 @ 07:24am
sure, you can use awPublic.prg!wFormMaster()


Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.






-- thn (FoxInCloud)

Gravatar is a globally recognized avatar based on your email address. Re: menus
  Tuvia Vinitsky
  Thierry Nivelet (FoxInCloud)
  Oct 20, 2014 @ 12:59pm
Note I am calling from JS code and thus am calling FoxInCloud.SomeMethod. .FormDisplay(event, "myform") displays a child form like wForm. What FoxInCloud method or parameters will result in a full background form?


sure, you can use awPublic.prg!wFormMaster()


Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.






Gravatar is a globally recognized avatar based on your email address. Re: menus
  FoxInCloud Support - Thierry N.
  Tuvia Vinitsky
  Oct 21, 2014 @ 01:00am
Using standard VFP menu commands and functions, form can/should be called on server side;
Here is a sample menu snippet code generated by awMenuGen, and adapted by FAA:
* *********************************************************
* *
* * _3XR0NKYZ7 ON SELECTION PAD
* *
* * Procedure Origin:
* *
* * From Menu: BIOSILWEB.MPR, Record: 4
* * Called By: ON SELECTION PAD
* * Prompt: Agenda
* * Snippet: 2
* *
* *********************************************************
*

PROCEDURE _3xr0nkyz7
* Appel de l'opérateur de saisie
IF lire_session()
external form agenda
agenda = wForm('agenda.scx', .T., DATE()+1) && could be agenda = wFormMaster('agenda.scx', DATE()+1)

*-FIC- After commenting this instruction, FoxInCloud Adaptation Assistant will replace
*-FIC- it by the two following instructions:
*-FIC- EXTERNAL FORM <form.scx> && Instructs project manager to include form.scx
*-FIC- whereas it's no longer explicitely declared by instruction DO FORM
*-FIC- [form] = wForm(<form.scx>, [, t01,...,t20]]) && the 'form' variable is not
*-FIC- created if DO FORM ... NAME ...
*-FIC- Please note that calling a modal form with user response (DO FORM ... TO ...)
*-FIC- is supported only in form member methods, not in independent procedure and
*-FIC- functions.
*-FIC- In Web mode, wForm() displays the form in a child window located in current
*-FIC- HTML page; if you prefer display the form in a new HTML page, replace 'wForm'
*-FIC- by 'wFormMaster'.


*-FIC- Replaced by FoxInCloud Adaptation Assistant version 2.00 beta1 (copy mode) on 10/10/13 14:13:56
*-FIC- DO FORM agenda WITH DATE()+1


Note I am calling from JS code and thus am calling FoxInCloud.SomeMethod. .FormDisplay(event, "myform") displays a child form like wForm. What FoxInCloud method or parameters will result in a full background form?


sure, you can use awPublic.prg!wFormMaster()


Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.







Gravatar is a globally recognized avatar based on your email address. Re: menus
  Tuvia Vinitsky
  Thierry Nivelet (FoxInCloud)
  Oct 21, 2014 @ 10:11pm
I have hundreds of menu options, I wanted to keep using the current css menus until I have a chance to recreate the menu structure in a VFP menu. I have been using FoxInCloud.FormDisplay to do that.


Using standard VFP menu commands and functions, form can/should be called on server side;
Here is a sample menu snippet code generated by awMenuGen, and adapted by FAA:
* *********************************************************
* *
* * _3XR0NKYZ7 ON SELECTION PAD
* *
* * Procedure Origin:
* *
* * From Menu: BIOSILWEB.MPR, Record: 4
* * Called By: ON SELECTION PAD
* * Prompt: Agenda
* * Snippet: 2
* *
* *********************************************************
*

PROCEDURE _3xr0nkyz7
* Appel de l'opérateur de saisie
IF lire_session()
external form agenda
agenda = wForm('agenda.scx', .T., DATE()+1) && could be agenda = wFormMaster('agenda.scx', DATE()+1)

*-FIC- After commenting this instruction, FoxInCloud Adaptation Assistant will replace
*-FIC- it by the two following instructions:
*-FIC- EXTERNAL FORM <form.scx> && Instructs project manager to include form.scx
*-FIC- whereas it's no longer explicitely declared by instruction DO FORM
*-FIC- [form] = wForm(<form.scx>, [, t01,...,t20]]) && the 'form' variable is not
*-FIC- created if DO FORM ... NAME ...
*-FIC- Please note that calling a modal form with user response (DO FORM ... TO ...)
*-FIC- is supported only in form member methods, not in independent procedure and
*-FIC- functions.
*-FIC- In Web mode, wForm() displays the form in a child window located in current
*-FIC- HTML page; if you prefer display the form in a new HTML page, replace 'wForm'
*-FIC- by 'wFormMaster'.


*-FIC- Replaced by FoxInCloud Adaptation Assistant version 2.00 beta1 (copy mode) on 10/10/13 14:13:56
*-FIC- DO FORM agenda WITH DATE()+1


Note I am calling from JS code and thus am calling FoxInCloud.SomeMethod. .FormDisplay(event, "myform") displays a child form like wForm. What FoxInCloud method or parameters will result in a full background form?


sure, you can use awPublic.prg!wFormMaster()


Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.








Gravatar is a globally recognized avatar based on your email address. Re: menus
  FoxInCloud Support - Thierry N.
  Tuvia Vinitsky
  Oct 22, 2014 @ 01:09am
what I understand is: though you wish to move some day to the new FiC menu system based on VFP menu commands and function, for now you want to keep your former menu system and get the ability to call a master form from a menu option.
do i understand correctly?

if this is correct, you can use as your menu option click code:

window.location.href='wFormStandardPage.xxx?awForm=myForm.scx'

/* or, if you want to control the way form displays *//
window.location.href='myFormPage.xxx' // 'myFormPage' is a xxxProcess method getting the form's HTML through this.wFormHTML('myForm.scx')


I have hundreds of menu options, I wanted to keep using the current css menus until I have a chance to recreate the menu structure in a VFP menu. I have been using FoxInCloud.FormDisplay to do that.


Using standard VFP menu commands and functions, form can/should be called on server side;
Here is a sample menu snippet code generated by awMenuGen, and adapted by FAA:
* *********************************************************
* *
* * _3XR0NKYZ7 ON SELECTION PAD
* *
* * Procedure Origin:
* *
* * From Menu: BIOSILWEB.MPR, Record: 4
* * Called By: ON SELECTION PAD
* * Prompt: Agenda
* * Snippet: 2
* *
* *********************************************************
*

PROCEDURE _3xr0nkyz7
* Appel de l'opérateur de saisie
IF lire_session()
external form agenda
agenda = wForm('agenda.scx', .T., DATE()+1) && could be agenda = wFormMaster('agenda.scx', DATE()+1)

*-FIC- After commenting this instruction, FoxInCloud Adaptation Assistant will replace
*-FIC- it by the two following instructions:
*-FIC- EXTERNAL FORM <form.scx> && Instructs project manager to include form.scx
*-FIC- whereas it's no longer explicitely declared by instruction DO FORM
*-FIC- [form] = wForm(<form.scx>, [, t01,...,t20]]) && the 'form' variable is not
*-FIC- created if DO FORM ... NAME ...
*-FIC- Please note that calling a modal form with user response (DO FORM ... TO ...)
*-FIC- is supported only in form member methods, not in independent procedure and
*-FIC- functions.
*-FIC- In Web mode, wForm() displays the form in a child window located in current
*-FIC- HTML page; if you prefer display the form in a new HTML page, replace 'wForm'
*-FIC- by 'wFormMaster'.


*-FIC- Replaced by FoxInCloud Adaptation Assistant version 2.00 beta1 (copy mode) on 10/10/13 14:13:56
*-FIC- DO FORM agenda WITH DATE()+1


Note I am calling from JS code and thus am calling FoxInCloud.SomeMethod. .FormDisplay(event, "myform") displays a child form like wForm. What FoxInCloud method or parameters will result in a full background form?


sure, you can use awPublic.prg!wFormMaster()


Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.










-- thn (FoxInCloud)

Gravatar is a globally recognized avatar based on your email address. Re: menus
  Tuvia Vinitsky
  Thierry Nivelet (FoxInCloud)
  Oct 22, 2014 @ 12:18pm
Perfect. Thanks.


what I understand is: though you wish to move some day to the new FiC menu system based on VFP menu commands and function, for now you want to keep your former menu system and get the ability to call a master form from a menu option.
do i understand correctly?

if this is correct, you can use as your menu option click code:

window.location.href='wFormStandardPage.xxx?awForm=myForm.scx'

/* or, if you want to control the way form displays *//
window.location.href='myFormPage.xxx' // 'myFormPage' is a xxxProcess method getting the form's HTML through this.wFormHTML('myForm.scx')


I have hundreds of menu options, I wanted to keep using the current css menus until I have a chance to recreate the menu structure in a VFP menu. I have been using FoxInCloud.FormDisplay to do that.


Using standard VFP menu commands and functions, form can/should be called on server side;
Here is a sample menu snippet code generated by awMenuGen, and adapted by FAA:
* *********************************************************
* *
* * _3XR0NKYZ7 ON SELECTION PAD
* *
* * Procedure Origin:
* *
* * From Menu: BIOSILWEB.MPR, Record: 4
* * Called By: ON SELECTION PAD
* * Prompt: Agenda
* * Snippet: 2
* *
* *********************************************************
*

PROCEDURE _3xr0nkyz7
* Appel de l'opérateur de saisie
IF lire_session()
external form agenda
agenda = wForm('agenda.scx', .T., DATE()+1) && could be agenda = wFormMaster('agenda.scx', DATE()+1)

*-FIC- After commenting this instruction, FoxInCloud Adaptation Assistant will replace
*-FIC- it by the two following instructions:
*-FIC- EXTERNAL FORM <form.scx> && Instructs project manager to include form.scx
*-FIC- whereas it's no longer explicitely declared by instruction DO FORM
*-FIC- [form] = wForm(<form.scx>, [, t01,...,t20]]) && the 'form' variable is not
*-FIC- created if DO FORM ... NAME ...
*-FIC- Please note that calling a modal form with user response (DO FORM ... TO ...)
*-FIC- is supported only in form member methods, not in independent procedure and
*-FIC- functions.
*-FIC- In Web mode, wForm() displays the form in a child window located in current
*-FIC- HTML page; if you prefer display the form in a new HTML page, replace 'wForm'
*-FIC- by 'wFormMaster'.


*-FIC- Replaced by FoxInCloud Adaptation Assistant version 2.00 beta1 (copy mode) on 10/10/13 14:13:56
*-FIC- DO FORM agenda WITH DATE()+1


Note I am calling from JS code and thus am calling FoxInCloud.SomeMethod. .FormDisplay(event, "myform") displays a child form like wForm. What FoxInCloud method or parameters will result in a full background form?


sure, you can use awPublic.prg!wFormMaster()


Got it, thanks.

Until I move menus back to VFP, I have been doing something like this:

<li onclick="FoxInCloud.FormDisplay(event, 'reports.scx')"><a href="#"><span>Reports</span></a></li>

But is there a FoxInCloud method equyivalent to wformmaster to create the page as a master page?


1. you could add to xxx.css:
.menubar.ui-widget-content {background: ...}

2. this is a mistake - fixed - thanks for the fb

3. The complete example is a couple of lines below (after COLOR SCHEME replacement)

Before executing commands such as
wMenu('ON PAD|BAR ... ACTIVATE MENU|POPUP xxx', @m.result)
wMenu('DEFINE MENU|POPUP xxx ...', @m.result)
wMenu('ACTIVATE MENU|POPUP ...', @m.result)
make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.

Sample code:

local success, result
result = CreateObject('Empty') && you create an object which defines the parameters that are required for your ON SELECTION commands and SKIP FOR expressions
success = .T.;
and AddProperty(m.result, 'loMyForm', thisForm);
and AddProperty(m.result, 'myValue', someValue);
and AddProperty(m.result, 'woCallBack', m.this);
and AddProperty(m.result, 'wcCallBack', 'wFormCallBack'); && this.wFormCallBack() will execute after user has made a choice
and wMenu('DEFI POPU myPopup MARGIN RELATIVE SHADOW COLOR W+/B*', @m.result);
and wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result);
and wMenu('ACTIVATE POPUP myPopup', @m.result) && m.result contains: on call, the 'parameter object'; on return, error message if any, otherwise unchanged
assert m.success message m.result

4. you choose the object where you want to define the call-back method - generally the most convenient is the object where the menu is defined.
This callback and the ON SELECTION methods are different; you can have a situation where you have
ACTIVATE POPUP
to let the user make a choice,
and the code located after ACTIVATE POPUP depends on the choice made by the user.
In this case, 2 methods are involved (as per the code above):
- loMyForm.myMethod() will store user choice, eg in some form.property
- this.wFormCallBack will execute based on form.property

1. VFP menus do not allow the main menu bar to have a color clause, I was hoping to create something like this image:

2. The documenation in awpublic shows COLOR SCHEME as an example of a legitimate paramater:

&& To adapt any menu command or function to LAN (desktop) mode and Web mode, pass it as a character string to wMenu();
&& FoxInCloud Adaptation Assistant adapts all your menu instructions that way

DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 && command before adaptation
wMenu('DEFI POPU myPopup MARGIN RELA SHADOW COLOR SCHEME 4 ') && command after adaptation
&& note: wMenu() expands standard abbreviated Visual FoxPro keywords and parses any number of spaces or tabs around clauses

3. I am not clear on the scope of the menu. If a menu is visible and I select an option that is supposed to call a method of a form, your example is:

wMenu('ON SELECTION BAR 2 OF myPopup loMyForm.myMethod(m.myValue)', @m.result)

What is the scope here? Is a menu tied to a specific form?

4. What callback object are you referring to here, which is where I was most unclear:

make sure to pass an object as second parameter [@m.result], with properties holding:
- any variable required for SKIP FOR and ON SELECTION clauses
- without the NOWAIT clause, the call-back object (.woCallBack) and method of this object (.wcCallBack) to be called:
. ACTIVATE MENU: after DEACTIVATE MENU
. ACTIVATE POPUP: when user has chosen an item from the menu
if either .woCallBack or .wcCallBack is not passed, the code you currently have after ACTIVATE MENU|POPUP will NOT get executed in Web mode.
Important! the call-back object (.woCallBack) MUST be a form or a form member.



1/ what are you not sure about?
You just need to pass your menu command or function as a litteral to wMenu()

2/ the COLOR clause is supported, not COLOR SCHEME


Does anyone have an example of a VFP menu they are using in FiC with skips, fonts, colors, etc? I read wmenu and have 2 issues:

1. Not sure the exact calling process

2. Have been using css menus with functions I wrote to refresh. It seems with the VFP menus in FiC I am still limited in design and appearance, for example bars cannot have colors.










© 1996-2024