* KIWAY Milestone A): Make major modules into DLL/DSOs.
! The initial testing of this commit should be done using a Debug build so that
all the wxASSERT()s are enabled. Also, be sure and keep enabled the
USE_KIWAY_DLLs option. The tree won't likely build without it. Turning it
off is senseless anyways. If you want stable code, go back to a prior version,
the one tagged with "stable".
* Relocate all functionality out of the wxApp derivative into more finely
targeted purposes:
a) DLL/DSO specific
b) PROJECT specific
c) EXE or process specific
d) configuration file specific data
e) configuration file manipulations functions.
All of this functionality was blended into an extremely large wxApp derivative
and that was incompatible with the desire to support multiple concurrently
loaded DLL/DSO's ("KIFACE")s and multiple concurrently open projects.
An amazing amount of organization come from simply sorting each bit of
functionality into the proper box.
* Switch to wxConfigBase from wxConfig everywhere except instantiation.
* Add classes KIWAY, KIFACE, KIFACE_I, SEARCH_STACK, PGM_BASE, PGM_KICAD,
PGM_SINGLE_TOP,
* Remove "Return" prefix on many function names.
* Remove obvious comments from CMakeLists.txt files, and from else() and endif()s.
* Fix building boost for use in a DSO on linux.
* Remove some of the assumptions in the CMakeLists.txt files that windows had
to be the host platform when building windows binaries.
* Reduce the number of wxStrings being constructed at program load time via
static construction.
* Pass wxConfigBase* to all SaveSettings() and LoadSettings() functions so that
these functions are useful even when the wxConfigBase comes from another
source, as is the case in the KICAD_MANAGER_FRAME.
* Move the setting of the KIPRJMOD environment variable into class PROJECT,
so that it can be moved into a project variable soon, and out of FP_LIB_TABLE.
* Add the KIWAY_PLAYER which is associated with a particular PROJECT, and all
its child wxFrames and wxDialogs now have a Kiway() member function which
returns a KIWAY& that that window tree branch is in support of. This is like
wxWindows DNA in that child windows get this member with proper value at time
of construction.
* Anticipate some of the needs for milestones B) and C) and make code
adjustments now in an effort to reduce work in those milestones.
* No testing has been done for python scripting, since milestone C) has that
being largely reworked and re-thought-out.
2014-03-20 00:42:08 +00:00
|
|
|
|
|
|
|
#include <colors.h>
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
* The predefined colors used in KiCad.
|
|
|
|
* Please: if you change a value, remember these values are carefully chosen
|
|
|
|
* to have good results in Pcbnew, that uses the ORed value of basic colors
|
|
|
|
* when displaying superimposed objects
|
|
|
|
* This list must have exactly NBCOLORS items
|
|
|
|
*/
|
|
|
|
const StructColors g_ColorRefs[NBCOLORS] =
|
|
|
|
{
|
|
|
|
{ 0, 0, 0, BLACK, wxT( "Black" ), DARKDARKGRAY },
|
|
|
|
{ 72, 72, 72, DARKDARKGRAY, wxT( "Gray 1" ), DARKGRAY },
|
|
|
|
{ 132, 132, 132, DARKGRAY, wxT( "Gray 2" ), LIGHTGRAY },
|
|
|
|
{ 194, 194, 194, LIGHTGRAY, wxT( "Gray 3" ), WHITE },
|
|
|
|
{ 255, 255, 255, WHITE, wxT( "White" ), WHITE },
|
|
|
|
{ 194, 255, 255, LIGHTYELLOW, wxT( "L.Yellow" ), WHITE },
|
|
|
|
{ 72, 0, 0, DARKBLUE, wxT( "Blue 1" ), BLUE },
|
|
|
|
{ 0, 72, 0, DARKGREEN, wxT( "Green 1" ), GREEN },
|
|
|
|
{ 72, 72, 0, DARKCYAN, wxT( "Cyan 1" ), CYAN },
|
|
|
|
{ 0, 0, 72, DARKRED, wxT( "Red 1" ), RED },
|
|
|
|
{ 72, 0, 72, DARKMAGENTA, wxT( "Magenta 1" ), MAGENTA },
|
|
|
|
{ 0, 72, 72, DARKBROWN, wxT( "Brown 1" ), BROWN },
|
|
|
|
{ 132, 0, 0, BLUE, wxT( "Blue 2" ), LIGHTBLUE },
|
|
|
|
{ 0, 132, 0, GREEN, wxT( "Green 2" ), LIGHTGREEN },
|
|
|
|
{ 132, 132, 0, CYAN, wxT( "Cyan 2" ), LIGHTCYAN },
|
|
|
|
{ 0, 0, 132, RED, wxT( "Red 2" ), LIGHTRED },
|
|
|
|
{ 132, 0, 132, MAGENTA, wxT( "Magenta 2" ), LIGHTMAGENTA },
|
|
|
|
{ 0, 132, 132, BROWN, wxT( "Brown 2" ), YELLOW },
|
|
|
|
{ 194, 0, 0, LIGHTBLUE, wxT( "Blue 3" ), PUREBLUE, },
|
|
|
|
{ 0, 194, 0, LIGHTGREEN, wxT( "Green 3" ), PUREGREEN },
|
|
|
|
{ 194, 194, 0, LIGHTCYAN, wxT( "Cyan 3" ), PURECYAN },
|
|
|
|
{ 0, 0, 194, LIGHTRED, wxT( "Red 3" ), PURERED },
|
|
|
|
{ 194, 0, 194, LIGHTMAGENTA, wxT( "Magenta 3" ), PUREMAGENTA },
|
|
|
|
{ 0, 194, 194, YELLOW, wxT( "Yellow 3" ), PUREYELLOW },
|
|
|
|
{ 255, 0, 0, PUREBLUE, wxT( "Blue 4" ), WHITE },
|
|
|
|
{ 0, 255, 0, PUREGREEN, wxT( "Green 4" ), WHITE },
|
|
|
|
{ 255, 255, 0, PURECYAN, wxT( "Cyan 4" ), WHITE },
|
|
|
|
{ 0, 0, 255, PURERED, wxT( "Red 4" ), WHITE },
|
|
|
|
{ 255, 0, 255, PUREMAGENTA, wxT( "Magenta 4" ), WHITE },
|
|
|
|
{ 0, 255, 255, PUREYELLOW, wxT( "Yellow 4" ), WHITE },
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
EDA_COLOR_T ColorByName( const wxString& aName )
|
|
|
|
{
|
|
|
|
// look for a match in the palette itself
|
|
|
|
for( EDA_COLOR_T trying = BLACK; trying < NBCOLORS; trying = NextColor(trying) )
|
|
|
|
{
|
|
|
|
if( 0 == aName.CmpNoCase( g_ColorRefs[trying].m_Name ) )
|
|
|
|
return trying;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Not found, no idea...
|
|
|
|
return UNSPECIFIED_COLOR;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
bool ColorIsLight( EDA_COLOR_T aColor )
|
|
|
|
{
|
|
|
|
const StructColors &c = g_ColorRefs[ColorGetBase( aColor )];
|
|
|
|
int r = c.m_Red;
|
|
|
|
int g = c.m_Green;
|
|
|
|
int b = c.m_Blue;
|
|
|
|
return ((r * r) + (g * g) + (b * b)) > (128 * 128 * 3);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
EDA_COLOR_T ColorFindNearest( const wxColour &aColor )
|
|
|
|
{
|
|
|
|
return ColorFindNearest( aColor.Red(), aColor.Green(), aColor.Blue() );
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
EDA_COLOR_T ColorFindNearest( int aR, int aG, int aB )
|
|
|
|
{
|
|
|
|
EDA_COLOR_T candidate = BLACK;
|
|
|
|
|
|
|
|
/* Find the 'nearest' color in the palette. This is fun. There is
|
|
|
|
a gazilion of metrics for the color space and no one of the
|
|
|
|
useful one is in the RGB color space. Who cares, this is a CAD,
|
|
|
|
not a photosomething...
|
|
|
|
|
|
|
|
I hereby declare that the distance is the sum of the square of the
|
|
|
|
component difference. Think about the RGB color cube. Now get the
|
|
|
|
euclidean distance, but without the square root... for ordering
|
|
|
|
purposes it's the same, obviously. Also each component can't be
|
|
|
|
less of the target one, since I found this currently work better...
|
|
|
|
*/
|
|
|
|
int nearest_distance = 255 * 255 * 3 + 1; // Can't beat this
|
|
|
|
|
|
|
|
for( EDA_COLOR_T trying = BLACK; trying < NBCOLORS; trying = NextColor(trying) )
|
|
|
|
{
|
|
|
|
const StructColors &c = g_ColorRefs[trying];
|
|
|
|
int distance = (aR - c.m_Red) * (aR - c.m_Red) +
|
|
|
|
(aG - c.m_Green) * (aG - c.m_Green) +
|
|
|
|
(aB - c.m_Blue) * (aB - c.m_Blue);
|
|
|
|
if( distance < nearest_distance && c.m_Red >= aR &&
|
|
|
|
c.m_Green >= aG && c.m_Blue >= aB )
|
|
|
|
{
|
|
|
|
nearest_distance = distance;
|
|
|
|
candidate = trying;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return candidate;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
EDA_COLOR_T ColorMix( EDA_COLOR_T aColor1, EDA_COLOR_T aColor2 )
|
|
|
|
{
|
|
|
|
/* Memoization storage. This could be potentially called for each
|
|
|
|
* color merge so a cache is useful (there are few colours anyway) */
|
|
|
|
static EDA_COLOR_T mix_cache[NBCOLORS][NBCOLORS];
|
|
|
|
|
|
|
|
// TODO how is alpha used? it's a mac only thing, I have no idea
|
|
|
|
aColor1 = ColorGetBase( aColor1 );
|
|
|
|
aColor2 = ColorGetBase( aColor2 );
|
|
|
|
|
|
|
|
// First easy thing: a black gives always the other colour
|
|
|
|
if( aColor1 == BLACK )
|
|
|
|
return aColor2;
|
Modular-Kicad milestone B), major portions:
*) Rework the set language support, simplify it by using KIWAY. Now any major
frame with a "change language" menu can change the language for all KIWAY_PLAYERs
in the whole KIWAY. Multiple KIWAYs are not supported yet.
*) Simplify "modal wxFrame" support, and add that support exclusively to
KIWAY_PLAYER where it is inherited by all derivatives. The function
KIWAY_PLAYER::ShowModal() is in the vtable and so is cross module capable.
*) Remove the requirements and assumptions that the wxFrame hierarchy always
had PCB_EDIT_FRAME and SCH_EDIT_FRAME as immediate parents of their viewers
and editors. This is no longer the case, nor required.
*) Use KIWAY::Player() everywhere to make KIWAY_PLAYERs, this registers the
KIWAY_PLAYER within the KIWAY and makes it very easy to find an open frame
quickly. It also gives control to the KIWAY as to frame hierarchical
relationships.
*) Change single_top to use the KIWAY for loading a KIFACE and instantiating
the single KIWAY_PLAYER, see bullet immediately above.
*) Add KIWAY::OnKiwayEnd() and call it from PGM_BASE at program termination, this
gives the KIFACEs a chance to save their final configuration dope to disk.
*) Add dedicated FRAME_T's for the modal frames, so m_Ident can be tested and
these modal frames are distinctly different than their non-modal equivalents.
KIWAY_PLAYER::IsModal() is !not! a valid test during the wxFrame's constructor,
so this is another important reason for having a dedicated FRAME_T for each
modal wxFrame.
On balance, more lines were deleted than were added to achieve all this.
2014-05-03 17:40:19 +00:00
|
|
|
|
* KIWAY Milestone A): Make major modules into DLL/DSOs.
! The initial testing of this commit should be done using a Debug build so that
all the wxASSERT()s are enabled. Also, be sure and keep enabled the
USE_KIWAY_DLLs option. The tree won't likely build without it. Turning it
off is senseless anyways. If you want stable code, go back to a prior version,
the one tagged with "stable".
* Relocate all functionality out of the wxApp derivative into more finely
targeted purposes:
a) DLL/DSO specific
b) PROJECT specific
c) EXE or process specific
d) configuration file specific data
e) configuration file manipulations functions.
All of this functionality was blended into an extremely large wxApp derivative
and that was incompatible with the desire to support multiple concurrently
loaded DLL/DSO's ("KIFACE")s and multiple concurrently open projects.
An amazing amount of organization come from simply sorting each bit of
functionality into the proper box.
* Switch to wxConfigBase from wxConfig everywhere except instantiation.
* Add classes KIWAY, KIFACE, KIFACE_I, SEARCH_STACK, PGM_BASE, PGM_KICAD,
PGM_SINGLE_TOP,
* Remove "Return" prefix on many function names.
* Remove obvious comments from CMakeLists.txt files, and from else() and endif()s.
* Fix building boost for use in a DSO on linux.
* Remove some of the assumptions in the CMakeLists.txt files that windows had
to be the host platform when building windows binaries.
* Reduce the number of wxStrings being constructed at program load time via
static construction.
* Pass wxConfigBase* to all SaveSettings() and LoadSettings() functions so that
these functions are useful even when the wxConfigBase comes from another
source, as is the case in the KICAD_MANAGER_FRAME.
* Move the setting of the KIPRJMOD environment variable into class PROJECT,
so that it can be moved into a project variable soon, and out of FP_LIB_TABLE.
* Add the KIWAY_PLAYER which is associated with a particular PROJECT, and all
its child wxFrames and wxDialogs now have a Kiway() member function which
returns a KIWAY& that that window tree branch is in support of. This is like
wxWindows DNA in that child windows get this member with proper value at time
of construction.
* Anticipate some of the needs for milestones B) and C) and make code
adjustments now in an effort to reduce work in those milestones.
* No testing has been done for python scripting, since milestone C) has that
being largely reworked and re-thought-out.
2014-03-20 00:42:08 +00:00
|
|
|
if( aColor2 == BLACK)
|
|
|
|
return aColor1;
|
|
|
|
|
|
|
|
/* Now we are sure that black can't occur, so the rule is:
|
|
|
|
* BLACK means not computed yet. If we're lucky we already have
|
|
|
|
* an answer */
|
|
|
|
EDA_COLOR_T candidate = mix_cache[aColor1][aColor2];
|
|
|
|
if( candidate != BLACK )
|
|
|
|
return candidate;
|
|
|
|
|
|
|
|
// Blend the two colors (i.e. OR the RGB values)
|
|
|
|
const StructColors &c1 = g_ColorRefs[aColor1];
|
|
|
|
const StructColors &c2 = g_ColorRefs[aColor2];
|
|
|
|
|
|
|
|
// Ask the palette for the nearest color to the mix
|
|
|
|
wxColour mixed( c1.m_Red | c2.m_Red,
|
|
|
|
c1.m_Green | c2.m_Green,
|
|
|
|
c1.m_Blue | c2.m_Blue );
|
|
|
|
candidate = ColorFindNearest( mixed );
|
|
|
|
|
|
|
|
/* Here, BLACK is *not* a good answer, since it would recompute the next time.
|
|
|
|
* Even theorically its not possible (with the current rules), but
|
|
|
|
* maybe the metric will change in the future */
|
|
|
|
if( candidate == BLACK)
|
|
|
|
candidate = DARKDARKGRAY;
|
|
|
|
|
|
|
|
// Store the result in the cache. The operation is commutative, too
|
|
|
|
mix_cache[aColor1][aColor2] = candidate;
|
|
|
|
mix_cache[aColor2][aColor1] = candidate;
|
|
|
|
return candidate;
|
|
|
|
}
|
|
|
|
|