TabOptions switch "-SelectorColor" sets the colur permanently

[wpiotrw]

Hello

When TabOptions -SlimTabs -SelectorColor blue is used color is set permanently even after -selectorcolor switched is removed

So the only way to change the color is to use the switch -selectorcolor again with new color name.

• Is there a way to restore the color/layout to the deafault?
• any chance that -selectorcolor switch will support hexhtml colours values?

Piotr

[PrzemyslawKlys]

1. Please give an example how you're using this. As far as I understand the way it's supposed to be used is to have 1 selector for whole .HTML file but maybe there are other ways people use it
2. All commands that take color will give you validateset for colors, however if you give it HEX value it will be used.

The code responsible for it:

PSWriteHTML/Private/Convert-FromColor.ps1

Lines 1 to 31 in 3006545

	function ConvertFrom-Color {
	[alias('Convert-FromColor')]
	[CmdletBinding()]
	param (
	[ValidateScript( {
	if ($($_ -in $Script:RGBColors.Keys -or $_ -match "^#([A-Fa-f0-9]{6})$" -or $_ -eq "") -eq $false) {
	throw "The Input value is not a valid colorname nor an valid color hex code."
	} else { $true }
	})]
	[alias('Colors')][string[]] $Color,
	[switch] $AsDecimal
	)
	$Colors = foreach ($C in $Color) {
	$Value = $Script:RGBColors."$C"
	if ($C -match "^#([A-Fa-f0-9]{6})$") {
	return $C
	}
	if ($null -eq $Value) {
	return
	}
	$HexValue = Convert-Color -RGB $Value
	Write-Verbose "Convert-FromColor - Color Name: $C Value: $Value HexValue: $HexValue"
	if ($AsDecimal) {
	[Convert]::ToInt64($HexValue, 16)
	} else {
	"#$($HexValue)"
	}
	}
	$Colors
	}
	Register-ArgumentCompleter -CommandName ConvertFrom-Color -ParameterName Color -ScriptBlock { $Script:RGBColors.Keys }

Ferwe/Tino did hard work on that here #68

[wpiotrw]

Here u go

Extract:

TabOptions -SlimTabs -selectorcolor blue
Tab -Name 'Azure Service Health Dashboard' {
foreach ($Region in $Azure.Keys) {
Tab -Name $Region {
Table -DataTable $Azure.$Region -Filtering {
foreach ($Column in $Azure...

1. Selectorcolor switch added with blue as value
2. Generate the html
3. Remove the selector switch
4. Generate the html again. U will observe that color is still set as blue

Workaround:

• running new PS ISE session , import module and generate html again with default colours

Re validateset

• it is not applicable for -selectorcolor switch
• hex value did not work for me either

[PrzemyslawKlys]

I see. This is a bug. Will fix

It's related to how hashtable $Script:Configuration is able to survive runs.

PSWriteHTML/Private/Parameters.Configuration.ps1

Lines 397 to 428 in 3006545

	Tabbis = @{
	Comment = 'Elastic Tabbis'
	HeaderAlways = @{
	Css = "$PSScriptRoot\..\Resources\CSS\tabbis.css"
	}
	FooterAlways = @{
	JS = @(
	"$PSScriptRoot\..\Resources\JS\tabbis.js"
	"$PSScriptRoot\..\Resources\JS\tabbisAdditional.js"
	)
	}
	CustomActionsReplace = @{
	'ColorSelector' = ConvertFrom-Color -Color "DodgerBlue"
	'ColorTarget' = ConvertFrom-Color -Color "MediumSlateBlue"
	}
	}
	TabbisGradient = @{
	Comment = 'Elastic Tabs Gradient'
	FooterAlways = @{
	Css = "$PSScriptRoot\..\Resources\CSS\tabs-elastic.gradient.css"
	}
	CustomActionsReplace = @{
	'ColorSelector' = ConvertFrom-Color -Color "DodgerBlue"
	'ColorTarget' = ConvertFrom-Color -Color "MediumSlateBlue"
	}
	}
	TabbisTransition = @{
	Comment = 'Elastic Tabs Transition'
	FooterAlways = @{
	Css = "$PSScriptRoot\..\Resources\CSS\tabs-elastic.transition.css"
	}
	}

The workaround is to actually use: Import-Module PSWriteHTML -Force at the top which reloads module clearing hashtable - a reason why I didn't notice the error.

[wpiotrw]

Yep. That is why i showed workaround :)

On Wed, 27 May 2020 at 22:39, Przemysław Kłys ***@***.***> wrote: I see. This is a bug. Will fix It's related to how hashtable $Script:Configuration is able to survive runs. https://github.com/EvotecIT/PSWriteHTML/blob/30065455bfd08032a30217aba9b3a9cb0d2273c8/Private/Parameters.Configuration.ps1#L413-L422 The workaround is to actually use: Import-Module PSWriteHTML -Force at the top which reloads module clearing hashtable - a reason why I didn't notice the error. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#128 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI25TFMVEHR2ECJG7S5RSVLRTV275ANCNFSM4NMGIQ3Q> .

-- Best Regards / Pozdrawiam Piotr

[wpiotrw]

Any update pls? :)

[PrzemyslawKlys]

It should be fixed in next release.