# Pixelblaze V3.19 beta

**URL:** <https://forum.electromage.com/t/pixelblaze-v3-19-beta/1597>\
**Category:** Feature Ideas + Requests\
**Tags:** v3, beta\
**Created:** [September 23, 2021, 11:22pm UTC](https://forum.electromage.com/t/pixelblaze-v3-19-beta/1597 "2021-09-23T23:22:34Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Scruffynerf](https://forum.electromage.com/letter_avatar_proxy/v4/letter/s/34f0e0/32.png) [@Scruffynerf](https://forum.electromage.com/u/Scruffynerf)\
**Post date:** [September 25, 2021, 2:50pm UTC](https://forum.electromage.com/t/pixelblaze-v3-19-beta/1597/12 "2021-09-25T14:50:40Z")

</div>

we’re on the same wavelength. Yes, a 0xFFFF.FFFF would be ideal, but in the meantime, you could do a function:

```auto
function p(a,b){
    return a + (b >>16)
}

so...
 ary = [p(0xFDB9,0x7531), ...]

```

that was my thought in this [comment](https://forum.electromage.com/t/color-palette-support/192/18)

For slightly more readability with 4 256 values, you could do:

```auto
function p(a,b,c,d){
    return (a << 8) + b + (c >> 8) + (d >> 16)
}

so...
 ary = [p(0,255,128,0), p(0x0,0xFF,0x80,0x0)...]

```

I think I got the bit shift math right there, but double check me. And the forum parser doesn’t seem to like it.

---

_[View the full topic](https://forum.electromage.com/t/pixelblaze-v3-19-beta/1597)._