REDEFINE SAY on Buttonbar

[Enrico Maria Giordano]

You changed your look again!

[TimStone]

Enrico,

Code: Select all  Expand view

  REDEFINE BUTTONBAR oBarInv ID 100 SIZE 60,55 OF oDiw 2015
          oBarInv:bClrGrad := aPubGrad

Adding this per your example:

Code: Select all  Expand view

   oDiw:oBarInv:bPainted = { || oDiw:oBarInv:Say( 5, 200, cIAMsg, , , , .T., .T. ) }

Creates an error: Message not found: TDIALOG:OBARINV

Also note, cIAMsg is a variable for the text to be displayed.

[Antonio Linares]

You changed your look again!

It is an AI created painting

[Antonio Linares]

Dear Tim,

Instead of:

oDiw:oBarInv:bPainted = { || oDiw:oBarInv:Say( 5, 200, cIAMsg, , , , .T., .T. ) }

use:

oDiw:oBar:bPainted = { || oDiw:oBar:Say( 5, 200, cIAMsg, , , , .T., .T. ) }

[Enrico Maria Giordano]

You changed your look again!

It is an AI created painting

Are you serious?

[Antonio Linares]

Yes, using https://www.myheritage.es/ai-time-machine/all-results

Its really amazing. It requires ten fotos of yourself and then it starts creating all kind of paintings.

That one seemed to me a very good one

AI is here more and more...

[Enrico Maria Giordano]

Great!

[TimStone]

Antonio,

I tried but it fails. The actual bar object is oBarInv

oBar does not exist so the error says there is no exported variable bPainted ...

Tim

[Enrico Maria Giordano]

Try

Code: Select all  Expand view

oBarInv:bPainted = { || oBarInv:Say( 5, 200, cIAMsg, , , , .T., .T. ) }

[TimStone]

It doesn't show anything. It's not a huge problem, but I do see the REDEFINE SAY has limitations not found in @ ....SAY. Included in them is the inability to use a border.

[TimStone]

I was looking for a "cleaner" display ... but decided to go a different route.

I redefined my control from LTEXT to CTEXT and added the border to the resource ( in the .rc, WS_BORDER )

It looks decent and will work OK ...

[Enrico Maria Giordano]

It doesn't show anything.

We need a code sample showing the problem in order to help you.

[TimStone]

Enrico,

Marc's example, as stated before, shows the exact problem.

It is a very simple problem.
1). You have a variable, ie. abc := "Test One", and you might change it to abc := "Test two" when executing a process in the program.
2). You have a button bar which is using a gradient background.
3). You want to display the content of the variable at some place on the button bar. It needs to be after the buttons.
4). You want the text to appear on the button bar without a background because you want the gradient to be uninterrupted.
5). Using a SAY command with a CTEXT control in an RC file, you get the text ( which changes as the variable is reset ).
6). The SAY command defaults to the Windows Style background that we are using rather than allowing the gradient background to show through.
7). The use of TRANSPARENT, no matter how it is implemented, does not work to achieve this objective.
. If you look above the browse on Marc's example, you see the exact problem. The word Test has a background around it different than the dialog, and thus stands out.

As I said, I ended up just putting a border around it so it doesn't look as bad. It would be nice to have the ability to write text on a button bar where just the text is displayed and not the background.

For now, I will simply use my current display, and maybe at some point this can be addressed in FWH code.

[Enrico Maria Giordano]

Enrico,

Marc's example, as stated before, shows the exact problem.

I've already shown a workaround for that problem.

[TimStone]

I tried your workaround. However I am using RESOURCES for the control. It didn't work.