Visual Studio Add-RGB Macro Creator

Environment: VC6 SP5, W2K SP3

This addin supports one command: ColorSelectorCommand. The addin shows a standard ColorSelect dialog and forms text that looks like an RGB-macro string (RGB(100, 120, 130)). Before the dialog is shown, the addin checks the current selection. If the selection starts with "RGB," the current color in the dialog will be set to those RGB values.

Gert-Jan de Vos has decided to add some features:

  • The selector now provides a choice for RGB(), hex, or HTML format color output—(RGB(255, 128, 64), 0x4080FF, #FF8040)
  • It recognises any of the supported formats in the source.
  • It recognises input if the cursor is anywhere in the color text.
  • It adds a toolbar button.

The addin became much better after its additions. I only have changed a little RGB-processing and have added a check on hex-values. Now the addin also can processes strings of the RGB(0xFF, 0x80, 0x40) kind.

Also, I have added a function "pipette" to define the color of a point in any place on the screen.

Note: For definition of color outside Windows' Visual Studio, it is necessary to hold down the left mouse button.

Downloads

Download addin - 19 Kb
Download source - 28 Kb


Comments

  • addauto.h' isn't in the project

    Posted by alost on 01/23/2008 04:49am

    Loading snd building the project give the message: Compiling... StdAfx.cpp WINVER not defined. Defaulting to 0x0600 (Windows Vista) c:\avo\colorselector_src\stdafx.h(21) : fatal error C1083: Cannot open include file: 'ObjModel\addauto.h': No such file or directory Build log was saved at "file://C:\avo\ColorSelector_src\Debug\BuildLog.htm" ColorSelector - 1 error(s), 0 warning(s)

    Reply
  • Crashes VS if no document open.

    Posted by Legacy on 08/28/2003 12:00am

    Originally posted by: Erich W. Einfalt

    If no source code document is open, the toolbar icon still shows to be enabled. If the icon is clicked when no source code document is open, an access violation dialog appears:

    "...instruction at address 0x100041de tried to access memory at 0x00000000. Memory could not be 'read'"

    If no document is open, the toolbar icon should be disabled.

    Reply
  • Woooooooow!! Amazing!!!

    Posted by Legacy on 08/26/2003 12:00am

    Originally posted by: EF

    This the most usfull addin I ever seen!!!

    Goooooooooood Work!!

    Reply
  • Grreat Work

    Posted by Legacy on 08/06/2003 12:00am

    Originally posted by: Nice Life

    Great Idea!!

    Reply
  • Any links to guidelines

    Posted by Legacy on 08/05/2003 12:00am

    Originally posted by: Kiran

    Any links to guidelines to develop an add-in ?

    Thanks,
    Kiran

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • It's time high-level executives and IT compliance officers recognize and acknowledge the danger of malicious insiders, an increased attack surface and the potential for breaches caused by employee error or negligence. See why there is extra emphasis on insider threats.

  • Live Event Date: May 6, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT While you likely have very good reasons for remaining on WinXP after end of support -- an estimated 20-30% of worldwide devices still are -- the bottom line is your security risk is now significant. In the absence of security patches, attackers will certainly turn their attention to this new opportunity. Join Lumension Vice President Paul Zimski in this one-hour webcast to discuss risk and, more importantly, 5 pragmatic risk mitigation techniques …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds