# User ColourIDs

**URL:** <https://forum.juce.com/t/user-colourids/4783>\
**Category:** General JUCE discussion\
**Created:** [January 26, 2010, 5:05pm UTC](https://forum.juce.com/t/user-colourids/4783 "2010-01-26T17:05:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaydee](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@jaydee](https://forum.juce.com/u/jaydee)\
**Post date:** [January 26, 2010, 5:05pm UTC](https://forum.juce.com/t/user-colourids/4783/1 "2010-01-26T17:05:08Z")

</div>

Forgive me if this is documented somewhere, or a silly question… but is there any specification for what enum we can start our own ColourIDs?

I notice JUCE uses 0x1\*\*\*\*\*\*, if I start using 0x2\*\*\*\*\*\* would that be safe?

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [January 26, 2010, 8:20pm UTC](https://forum.juce.com/t/user-colourids/4783/2 "2010-01-26T20:20:40Z")

</div>

Yes, I’m sure that’d be ok.

---

<div class="post-metadata">

**Author:** ![yfede](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/yfede/32/506_2.png) [@yfede](https://forum.juce.com/u/yfede)\
**Post date:** [January 26, 2010, 8:25pm UTC](https://forum.juce.com/t/user-colourids/4783/3 "2010-01-26T20:25:13Z")

</div>

Good idea, why not making this a standard somehow enforced by the library? Or at least explicit…  
More or less like TCP ports, those \< 1024 are reserved to the system, the others are (more or less) available to userland programs.

---

<div class="post-metadata">

**Author:** ![willrice](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/willrice/32/55_2.png) [@willrice](https://forum.juce.com/u/willrice)\
**Post date:** [May 19, 2016, 7:41pm UTC](https://forum.juce.com/t/user-colourids/4783/4 "2016-05-19T19:41:56Z")

</div>

Is 0x2\*\*\*\*\*\* still a sensible range to use for application specific colourIds?