FwDArrow() NOT SHOW THE ARROW

FwDArrow() NOT SHOW THE ARROW

Postby Silvio.Falconi » Fri Dec 20, 2019 4:13 pm

Image

@ 06,50 GET aGet[2] VAR ncella SIZE 70,32 PIXEL;
of oFolder:aDialogs[1] FONT oLarge picture "9999";
BITMAP FwDArrow() ;
ACTION nil
Since from 1991/1992 ( fw for clipper Rel. 14.4 - Momos)
I use : FiveWin for Harbour November 2023 - January 2024 - Harbour 3.2.0dev (harbour_bcc770_32_20240309) - Bcc7.70 - xMate ver. 1.15.3 - PellesC - mail: silvio[dot]falconi[at]gmail[dot]com
User avatar
Silvio.Falconi
 
Posts: 7056
Joined: Thu Oct 18, 2012 7:17 pm

Re: FwDArrow() NOT SHOW THE ARROW

Postby nageswaragunupudi » Sat Dec 21, 2019 3:32 am

At present only a bmpfilename or resource name can be specified in the BITMAP clause.
Specifying a bitmap handle does not work.

We can suggest a workaround for now:
Code: Select all  Expand view

hBmp := FWDArrow()

@ 06,50 GET aGet[2] VAR ncella SIZE 70,32 PIXEL;
of oFolder:aDialogs[1] FONT oLarge picture "9999";
BITMAP LTrim( Str( hBmp ) ) ;
ACTION nil

// other controls

ACTIVATE DIALOG oDlg

DeleteObject( hBmp )
 


From the next version of FWH, we can specify a bitmap handle directly as in your original code posted above.
Regards

G. N. Rao.
Hyderabad, India
User avatar
nageswaragunupudi
 
Posts: 10633
Joined: Sun Nov 19, 2006 5:22 am
Location: India

Re: FwDArrow() NOT SHOW THE ARROW

Postby Silvio.Falconi » Sat Dec 21, 2019 11:51 am

I try also to simulate the btn of the combobox

Image

inserting
activate dialog ....on init aGet[2]:oBtn:nWidth:= 20 , ;
aGet[2]:oBtn:nLeft:=aget[2]:nWidth-20
but the button not is as the button of the combo as you can see the height is more small
any solution pls
Since from 1991/1992 ( fw for clipper Rel. 14.4 - Momos)
I use : FiveWin for Harbour November 2023 - January 2024 - Harbour 3.2.0dev (harbour_bcc770_32_20240309) - Bcc7.70 - xMate ver. 1.15.3 - PellesC - mail: silvio[dot]falconi[at]gmail[dot]com
User avatar
Silvio.Falconi
 
Posts: 7056
Joined: Thu Oct 18, 2012 7:17 pm

Re: FwDArrow() NOT SHOW THE ARROW

Postby Silvio.Falconi » Sat Dec 21, 2019 12:36 pm

On oldest application I used Btnget classo of Ramirez and it run ok instead of normal tget

@ 80,50 BTNGET aGet[3] VAR ncella SIZE 70,32 PIXEL;
of oFolder:aDialogs[1] FONT oLarge picture "9999";
ACTION NIL

Image

It build the button with arrow on the class

btnget class is not compatible with current tget because it create a button

with Ramirez's class the button is uniform at the get height and automatically forms the arrow.

Unfortunately he wants an old Tget class because the current tget class is not compatible with the class

For what I need, the button with the Ramirez class works more than the button made with the fwh tget because it is more homogeneous to the tget.

I think you can change the button in the fwh tget don't you think?
Since from 1991/1992 ( fw for clipper Rel. 14.4 - Momos)
I use : FiveWin for Harbour November 2023 - January 2024 - Harbour 3.2.0dev (harbour_bcc770_32_20240309) - Bcc7.70 - xMate ver. 1.15.3 - PellesC - mail: silvio[dot]falconi[at]gmail[dot]com
User avatar
Silvio.Falconi
 
Posts: 7056
Joined: Thu Oct 18, 2012 7:17 pm


Return to FiveWin for Harbour/xHarbour

Who is online

Users browsing this forum: Google [Bot] and 35 guests