>but I tried to make a class but I saw oTooltip on Windows class is not a classdata but only a variable static !!
I think Antonio told me it was done this way for speed.
>for the dialog how I can make it ?
The easiest way is to just use the ACTION clause of the button define. If you are already using that for something else, then you could use bRClicked instead.
I think to popup the dialog whenever the mouse is over it will be more complex. There is a bMMoved codeblock, and if you use a modal dialog this might work. But if you wanted a window or non-modal dialog this would probably pop them up multiple times as the mouse was moving over the button so you would have to set a flag to keep this from happening.
Regards,
James
dialog creation ..
- James Bott
- Posts: 4654
- Joined: Fri Nov 18, 2005 4:52 pm
- Location: San Diego, California, USA
- Contact:
Re: dialog creation ..
James,
oBtn1:bMMoved := {| nRow, nCol | MsgAlert( ALLTRIM( STR(nRow)), ALLTRIM( STR(nCol)) ) }
will show nRow and nCol from inside the Button.
That is the reason, I used :
oDlg:bMMoved := {| nRow, nCol | MsgAlert( ALLTRIM( STR(nRow)), ALLTRIM( STR(nCol)) ) }
in Relation to SAY-Screenpositions
that works.
I think, creating or changing a Class including Tests,
takes much more Time, than changing Buttons to SAYs, getting the desired Results.
I cannot do more, than showing working Samples.
Before I start to change something inside original FWH-source, I try to find Solutions without
any Changes.
Best Regards
Uwe
oBtn1:bMMoved := {| nRow, nCol | MsgAlert( ALLTRIM( STR(nRow)), ALLTRIM( STR(nCol)) ) }
will show nRow and nCol from inside the Button.
That is the reason, I used :
oDlg:bMMoved := {| nRow, nCol | MsgAlert( ALLTRIM( STR(nRow)), ALLTRIM( STR(nCol)) ) }
in Relation to SAY-Screenpositions
that works.
I think, creating or changing a Class including Tests,
takes much more Time, than changing Buttons to SAYs, getting the desired Results.
I cannot do more, than showing working Samples.
Before I start to change something inside original FWH-source, I try to find Solutions without
any Changes.
Best Regards
Uwe
Since 1995 ( the first release of FW 1.9 )
i work with FW.
If you have any questions about special functions, maybe i can help.
i work with FW.
If you have any questions about special functions, maybe i can help.
- James Bott
- Posts: 4654
- Joined: Fri Nov 18, 2005 4:52 pm
- Location: San Diego, California, USA
- Contact:
Re: dialog creation ..
Uwe,
I don't think he needs the row and col when using bMMoved. He just needs to popup something when the cursor is over the button. Something like this:
oBtn1:bMMoved := { || msgInfo() }
Regards,
James
I don't think he needs the row and col when using bMMoved. He just needs to popup something when the cursor is over the button. Something like this:
oBtn1:bMMoved := { || msgInfo() }
Regards,
James
Re: dialog creation ..
James,
I got it working with Buttons.
I will create a nice Sample for it with different Options.
The Popup is shown related to Button-position.
The Button-temperature is show on Popup-title
Optional autoclose or staying on Screen with Buttonactions.
1. Button / Temperature :
2. Button / Temperature :
3. Button / Temperature :
Optional :
Best Regards
Uwe
I got it working with Buttons.
I will create a nice Sample for it with different Options.
The Popup is shown related to Button-position.
The Button-temperature is show on Popup-title
Optional autoclose or staying on Screen with Buttonactions.
1. Button / Temperature :
2. Button / Temperature :
3. Button / Temperature :
Optional :
Best Regards
Uwe
Since 1995 ( the first release of FW 1.9 )
i work with FW.
If you have any questions about special functions, maybe i can help.
i work with FW.
If you have any questions about special functions, maybe i can help.