Visible Button in TPanel ?

Hi altogether

I have an old 16bit NE program, written in Delphi 1.x.
The problem is, there is a buttonbar (TPanel) with a hidden button. How can I enable/visible it ?

I open this baby with ExeScope 6.3 (as far as I know the only one ressourcenhacker which can open old 16bit NE files), but unhappily I cannot found the entry in the RCDATA to enable the button.

Is it possible to hack this proggi in another way ?


Greetings
Waspy

Did you try to use DeDe from DaFixer? I don't know if it will work on 16-bit apps, but try it.

The_Philosopher

However Borland Resource Workshop works on 16bit EXEs too

hi,

DeDe 3.10 cannot open D1 files

With Borland Ressource WorkShop it is no problem to open, but it is the same as ExeScope:
I don't know, how I can find the right entry to make the button visible and I don't know, which values to edit.
there are many tables like this:

TFORMBUTTON RCDATA LOADONCALL MOVEABLE DISCARDABLE
{
'54 50 46 30 0B 54 46 6F 72 6D 42 75 74 74 6F 6E'
'0A 46 6F 72 6D 42 75 74 74 6F 6E 04 4C 65 66 74'
'03 48 01 03 54 6F 70 02 69 05 57 69 64 74 68 03'
'5C 01 06 48 65 69 67 68 74 03 F2 00 0B 48 65 6C'
'70 43 6F 6E 74 65 78 74 03 01 04 0B 42 6F 72 64'
'65 72 49 63 6F 6E 73 0B 0C 62 69 53 79 73 74 65'
'6D 4D 65 6E 75 0A 62 69 4D 69 6E 69 6D 69 7A 65'
'00 07 43 61 70 74 69 6F 6E 06 0A 46 6F 72 6D 42'
'75 74 74 6F 6E 0A 46 6F 6E 74 2E 43 6F 6C 6F 72'
etc.....

any help

Greetings
*** waspy ***

Generally speaking, RCDATA are raw data; they can be ANSI quoted strings, unicode quoted strings, words or dwords (numerical values). Delphi stores as RCDATA the contents of DFM modules, that contain the forms' description and properties as showed by the Object Inspector. DFM modules are almost plain text, so you have to examine them in text form. This is the ASCII equivalent of the hex values posted by you:


5450 4630 0B54 466F 726D 4275 7474 6F6E TPF0.TFormButton
0A46 6F72 6D42 7574 746F 6E04 4C65 6674 .FormButton.Left
0348 0103 546F 7002 6905 5769 6474 6803 .H..Top.i.Width.
5C01 0648 6569 6768 7403 F200 0B48 656C \..Height....Hel
7043 6F6E 7465 7874 0301 040B 426F 7264 pContext....Bord
6572 4963 6F6E 730B 0C62 6953 7973 7465 erIcons..biSyste
6D4D 656E 750A 6269 4D69 6E69 6D69 7A65 mMenu.biMinimize
0007 4361 7074 696F 6E06 0A46 6F72 6D42 ..Caption..FormB
7574 746F 6E0A 466F 6E74 2E43 6F6C 6F72 utton.Font.Color

you can read the DaFixer papers about their significance (at http://www.balbaro.com/dafixer)

I'm not quite clear about your problem:is the button invisible or disabled?
Anyway, an alternative solution could lie in modifying the code (i.e. the parameters passed to IsWindowEnabled or IsWindowVisible functions)
Hope it helps

Originally posted by Vox Humana
I'm not quite clear about your problem:is the button invisible or disabled?
Anyway, an alternative solution could lie in modifying the code (i.e. the parameters passed to IsWindowEnabled or IsWindowVisible functions)
Hope it helps

Thank you very much for your anser !

It is a toolbar with an invisible button/gadget.
Yes, I think too, it is a better way to modify the asm-code.

greetings
*** waspy ****