This will make radasm's properties box more powerful .
This is screenshoot of propeties box in Visual Asm.
It can change font , back color, text color for button, form, stactic box ... for form and Controls in form.
Radasm need improve the properties box.
This improving will make radasm stronger and better, wiIl make form designing easier and fast . The programer don't need to write alot of code to set color to control like stactic box, it's easy like Design Form in Visual Basic.
you can see Visual ASM in :
http://www.geocities.com/technosoftt/Download.htm
This is screenshoot of propeties box in Visual Asm.
It can change font , back color, text color for button, form, stactic box ... for form and Controls in form.
Radasm need improve the properties box.
This improving will make radasm stronger and better, wiIl make form designing easier and fast . The programer don't need to write alot of code to set color to control like stactic box, it's easy like Design Form in Visual Basic.
you can see Visual ASM in :
http://www.geocities.com/technosoftt/Download.htm
This is Properties Box of Visual ASM
Hi neverending,
I suppose the change could be made but it would only be cosmetic. There is no way to avoid actually setting the fonts and colors inside your program. Even the examples in VASM do the same thing, they may look nice on the dialog but in reality the code must still be added. The limitation is in the DIALOGEX structure, it has no facility to individually set the color or font for controls. If you look closely at the examples in VASM the controls must be individually colored and have their fonts set:
They are limited in what they can do as well by the structure and limitations of the RC file format:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/tools/common_control_parameters.asp
so any changes to the dialog in the editor would only be in the editor, inside your program it would not be changed until you change it. The code still has to be written no matter what you do in the editor, the dialog cannot be created with these things already done.
I suppose the change could be made but it would only be cosmetic. There is no way to avoid actually setting the fonts and colors inside your program. Even the examples in VASM do the same thing, they may look nice on the dialog but in reality the code must still be added. The limitation is in the DIALOGEX structure, it has no facility to individually set the color or font for controls. If you look closely at the examples in VASM the controls must be individually colored and have their fonts set:
DlgProcForm Proc hWnd:HWND, uMsg:UINT, wParam:WPARAM, lParam:LPARAM
.If uMsg==WM_INITDIALOG
Invoke InitializeFlatSB,hWnd
Invoke FlatSB_ShowScrollBar,hWnd, SB_VERT, 1
Invoke GetDlgItem, hWnd,Check0
mov hCheck0,eax
.
.
.
Invoke CreateFont, 10 ,0,0,0,100,0,0,0,1,0,0,4,0,Offset FntNmCheck0
mov hFntCheck0,eax
Invoke SendMessage, hCheck0, WM_SETFONT, hFntCheck0, TRUE
Invoke CreateFont, 10 ,0,0,0,100,0,0,0,1,0,0,4,0,Offset FntNmCheck1
.
.
.
Invoke SendMessage,hSlider1,TBM_SETRANGE,0,03E8012Ch
Invoke SendMessage,hSlider1,TBM_SETTICFREQ,064h,0
Invoke SendMessage,hSlider2,TBM_SETRANGE,0,038401F4h
Invoke SendMessage,hSlider2,TBM_SETTICFREQ,032h,0
Invoke SendMessage,hProgress3,PBM_SETRANGE,0,03E80000h
Invoke SendMessage,hProgress3,PBM_SETPOS,01F4h,0
mov esi,14
mov edi,Offset ColCheck0
.Repeat
.If Dword Ptr[edi+8]==1
Invoke CreateSolidBrush,Dword Ptr[edi]
mov [edi+12],eax
.EndIf
add edi,16
dec esi
.Until esi==0
Invoke CreateSolidBrush, 0FF0000h
mov hColForm,eax
.ElseIf uMsg==WM_CTLCOLORDLG
mov eax,hColForm
ret
.ElseIf uMsg==WM_CTLCOLORSTATIC || uMsg==WM_CTLCOLORBTN \
|| uMsg==WM_CTLCOLOREDIT || uMsg==WM_CTLCOLORLISTBOX \
|| uMsg==WM_CTLCOLORSCROLLBAR
mov edi,Offset hCheck0
mov ecx,14
mov esi,ecx
mov ebx,Offset ColCheck0
mov eax,lParam
.Repeat
.If [edi]==eax
sub esi,ecx
shl esi,4
lea edi,[ebx][esi]
.If Dword Ptr[edi+8]==1
Invoke SetBkColor,wParam,Dword Ptr[edi]
Invoke SetTextColor,wParam,Dword Ptr[edi+4]
mov eax,[edi+12]
mov ebx,eax
Invoke SelectObject, wParam,eax
Invoke DeleteObject, eax
mov eax,ebx
.Else
xor eax,eax
.EndIf
ret
.EndIf
add edi,4
.UntilCXZ
.
.
.
DlgProcForm EndP
They are limited in what they can do as well by the structure and limitations of the RC file format:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/tools/common_control_parameters.asp
so any changes to the dialog in the editor would only be in the editor, inside your program it would not be changed until you change it. The code still has to be written no matter what you do in the editor, the dialog cannot be created with these things already done.