If you want to play with hues precisely, go to the maps API style wizard and select an element, select a 'pure' hue, (say, FF0000) in the hue bar using a colormetre to click the right colour (mac's OS- native 'DigitalColor Meter' is cool for this - set it to a 1px aperture), set the saturation bar to 100 (this makes damn sure that, no matter what the map's original setting was, the result will always be 100 (it can't be more). Then, testing with the colour metre, play with the gamma bar until the colour of the element you are modifying is the same as the pure hue you chose. This seems to create testing conditions that are constant across the board.
hex '0xff0000' = dec '16711680' ... doh! Gives the same results when submitted as a hue. #225 = #000225 : yep, always the case - 'missing' hex characters (out of the mandatory six) are automatically appended after the '#' (#FF == #0000FF) - but you know this ; ) 0x225 = 0x000225 gives the same results as well, for the record. But why the different results between '#255' and '0x255'? They behave in the same way... I think Google is expecting something different. I tried prepending 'FF' (the oft-appearing Google 'gamma factor' mentioned elsewhere in this thread), but no go... is google perhaps expecting a 16-bit hex number? On Aug 26, 10:12 am, "William ." <[email protected]> wrote: > On Wed, Aug 25, 2010 at 6:59 PM, Sefu <[email protected]> wrote: > > ... yet '225' renders magenta, '#225' renders blue, and '0x225' > > renders purple > > Obviously these are undocumented properties and cannot be relied upon in a > production system, but I believe that: > 1. '225' and '0x225' are relative hues, specified in decimal degrees, > applied as an adjustment to the existing color in ROADMAP, and > 2. '#225' is an absolute rgb hue, which replaces the existing color in > ROADMAP > > RELATIVE HUES > > 225 is decimal already, and > 0x225 hex = 549 decimal, which is 360 + 189 > > so on an example with roads where the shaded color is yellow, 60 degrees, > then the expected hues are calculated by adding the shift to 60: > > (a) 225 + 60 = 285 > (b) 189 + 60 = 249 > > when I tried it (with saturation 100) and then selected the resulting colors > with photoshop it said 284 and 248 respectively, very close to the predicted > hue. > > ABSOLUTE HUES > > I think '#225' is interpreted with leading zeros to pad to 6 hex digits = > '#000225' > photoshop says this is a hue of 237 degrees. This is confirmed when trying > hue: '#225' on roads (with saturation: 100) > > ... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
