SetCtlColors with variables - Revision history

Anders: Not x64 compatible

2017-11-04T19:14:29Z

Not x64 compatible

â† Older revision		Revision as of 19:14, 4 November 2017
Line 18:		Line 18:
	Push $R4		Push $R4

			!if "${NSIS_PTR_SIZE}" > 4
			!error "TODO: Not 64-bit compatible, 64-bit uses a different ctlcolors struct"
			!endif
	!define ctlcolors (i,i,i,i,i,i)i		!define ctlcolors (i,i,i,i,i,i)i
	!define BS_SOLID 0		!define BS_SOLID 0

Afrow UK: /* Usage */

2010-05-28T15:32:39Z

Usage

â† Older revision		Revision as of 15:32, 28 May 2010
Line 82:		Line 82:
	</highlight-nsis>		</highlight-nsis>
	The above code is the same as SetCtlColors $R0 0xFF0000 0x00FF00.		The above code is the same as SetCtlColors $R0 0xFF0000 0x00FF00.
	Notice the System::Free call at the end in .onGUIEnd. You will have a memory leak if you don't use it.		Notice the System::Free call at the end in .onGUIEnd. You will have a memory leak if you don't use it. Also note that for each call to SetCtlColors you will need a new SetCtlColorsVar to store a pointer to the allocated memory. Reusing SetCtlColorsVar1 (in this example) is not an option.

	[[Category:Functions_&_Macros]]		[[Category:Functions_&_Macros]]

Afrow UK: /* Usage */

2010-05-28T15:30:25Z

Usage

â† Older revision		Revision as of 15:30, 28 May 2010
Line 71:		Line 71:
	GetDlgItem $R0 $R0 1006		GetDlgItem $R0 $R0 1006

	${SetCtlColors} $R0 ~~0xFF0000 0x00FF00~~ $SetCtlColorsVar1		StrCpy $R1 0xFF0000
			StrCpy $R2 0x00FF00
			${SetCtlColors} $R0 $R1 $R2 $SetCtlColorsVar1

	SectionEnd		SectionEnd
Line 79:		Line 81:
	FunctionEnd		FunctionEnd
	</highlight-nsis>		</highlight-nsis>
			The above code is the same as SetCtlColors $R0 0xFF0000 0x00FF00.
	Notice the System::Free call at the end in .onGUIEnd. You will have a memory leak if you don't use it.		Notice the System::Free call at the end in .onGUIEnd. You will have a memory leak if you don't use it.

	[[Category:Functions_&_Macros]]		[[Category:Functions_&_Macros]]

Afrow UK at 15:00, 28 May 2010

2010-05-28T15:00:37Z

â† Older revision		Revision as of 15:00, 28 May 2010
Line 1:		Line 1:
	{{PageAuthor:Afrow UK}}		{{PageAuthor\|Afrow UK}}

	== Description ==		== Description ==

Afrow UK: Created page with '{{PageAuthor:Afrow UK}} == Description == This is an alternative to the built-in SetCtlColors which allows variables for the colours. It does not support /BRANDING but it does s…'

2010-05-28T14:59:57Z

Created page with '{{PageAuthor:Afrow UK}} == Description == This is an alternative to the built-in SetCtlColors which allows variables for the colours. It does not support /BRANDING but it does s…'

New page

{{PageAuthor:Afrow UK}}

== Description ==
This is an alternative to the built-in SetCtlColors which allows variables for the colours. It does not support /BRANDING but it does support "transparent" for the background colour.

The reason the built-in SetCtlColors does not support variables is because it converts the given colours from RGB to BGR (required for COLORREF) at compile time before storing the converted values in the executable header inside a "ctlcolors" structure. My function simulates the code that is built into NSIS by allocating its own ctlcolors structure and passing its memory pointer to the chosen control using SetWindowLong/GWL_USERDATA. For this reason, the instance of the ctlcolors structure must remain in memory until the control is destroyed, or to be on the safe side, until .onGUIEnd is called. If we free the allocated memory any sooner (System::Free), NSIS can't read from the ctlcolors structure and a memory access violation will occur.

== The Function ==
<highlight-nsis>
Function SetCtlColors
Exch $R0
Exch
Exch $R1
Exch
Exch 2
Exch $R2
Push $R3
Push $R4

!define ctlcolors (i,i,i,i,i,i)i
!define BS_SOLID 0
!define BS_NULL 1
!define TRANSPARENT 1
!define OPAQUE 2
!define CC_TEXT 1
!define CC_BK 4
!define CC_BKB 16
!define GWL_USERDATA -21

!macro RGB2BGR Var
IntOp $R3 ${Var} & 0xFF
IntOp $R3 $R3 << 16
IntOp $R4 ${Var} & 0xFF00
IntOp $R3 $R3 | $R4
IntOp $R4 ${Var} & 0xFF0000
IntOp $R4 $R4 >> 16
IntOp ${Var} $R3 | $R4
!macroend

!insertmacro RGB2BGR $R1
${If} $R0 == transparent
System::Call *${ctlcolors}(R1,0,${BS_NULL},0,${TRANSPARENT},${CC_TEXT}|${CC_BKB}).R0
${Else}
!insertmacro RGB2BGR $R0
System::Call *${ctlcolors}(R1,R0,${BS_SOLID},0,${OPAQUE},${CC_TEXT}|${CC_BK}|${CC_BKB}).R0
${EndIf}
System::Call user32::SetWindowLong(iR2,i${GWL_USERDATA},lR0)

Pop $R4
Pop $R3
Pop $R2
Pop $R1
Exch $R0
FunctionEnd
!macro SetCtlColors Hwnd Text Background Memory
Push ${Hwnd}
Push ${Text}
Push ${Background}
Call SetCtlColors
Pop ${Memory}
!macroend
!define SetCtlColors `!insertmacro SetCtlColors`
</highlight-nsis>
== Usage ==
<highlight-nsis>
Var SetCtlColorsVar1

Section

FindWindow $R0 `#32770` `` $HWNDPARENT
GetDlgItem $R0 $R0 1006

${SetCtlColors} $R0 0xFF0000 0x00FF00 $SetCtlColorsVar1

SectionEnd

Function .onGUIEnd
System::Free $SetCtlColorsVar1
FunctionEnd
</highlight-nsis>
Notice the System::Free call at the end in .onGUIEnd. You will have a memory leak if you don't use it.

[[Category:Functions_&_Macros]]