2013-07-28 22:08:34 +00:00
|
|
|
//-----------------------------------------------------------------------------
|
|
|
|
// Entry point in to the program, our registry-stored settings and top-level
|
|
|
|
// housekeeping when we open, save, and create new files.
|
|
|
|
//
|
|
|
|
// Copyright 2008-2013 Jonathan Westhues.
|
|
|
|
//-----------------------------------------------------------------------------
|
2008-03-25 10:02:13 +00:00
|
|
|
#include "solvespace.h"
|
2016-04-23 23:00:16 +00:00
|
|
|
#include "config.h"
|
2008-03-25 10:02:13 +00:00
|
|
|
|
2015-03-27 15:31:23 +00:00
|
|
|
SolveSpaceUI SolveSpace::SS = {};
|
|
|
|
Sketch SolveSpace::SK = {};
|
2008-03-25 10:02:13 +00:00
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
std::string SolveSpace::RecentFile[MAX_RECENT] = {};
|
|
|
|
|
2015-03-24 06:45:53 +00:00
|
|
|
void SolveSpaceUI::Init() {
|
2016-07-25 19:37:48 +00:00
|
|
|
#if !defined(HEADLESS)
|
Implement a resource system.
Currently, icons, fonts, etc are converted to C structures at compile
time and are hardcoded to the binary. This presents several problems:
* Cross-compilation is complicated. Right now, it is necessary
to be able to run executables for the target platform; this
happens to work with wine-binfmt installed, but is rather ugly.
* Icons can only have one resolution. On OS X, modern software is
expected to take advantage of high-DPI ("Retina") screens and
use so-called @2x assets when ran in high-DPI mode.
* Localization is complicated. Win32 and OS X provide built-in
support for loading the resource appropriate for the user's
locale.
* Embedding strings can only be done as raw strings, using C++'s
R"(...)" literals. This precludes embedding sizable strings,
e.g. JavaScript libraries as used in Three.js export, and makes
git history less useful. Not embedding the libraries means we
have to rely on external CDNs, which requires an Internet
connection and adds a glaring point of failure.
* Linux distribution guidelines are violated. All architecture-
independent data, especially large data such as fonts, is
expected to be in /usr/share, not in the binary.
* Customization is impossible without recompilation. Minor
modifications like adding a few missing vector font characters
or adjusting localization require a complete development
environment, which is unreasonable to expect from users of
a mechanical CAD.
As such, this commit adds a resource system that bundles (and
sometimes builds) resources with the executable. Where they go is
platform-dependent:
* on Win32: into resources of the executable, which allows us to
keep distributing one file;
* on OS X: into the app bundle;
* on other *nix: into /usr/share/solvespace/ or ../res/ (relative
to the executable path), the latter allowing us to run freshly
built executables without installation.
It also subsides the platform-specific resources that are in src/.
The resource system is not yet used for anything; this will be added
in later commits.
2016-04-21 15:54:18 +00:00
|
|
|
// Check that the resource system works.
|
|
|
|
dbp("%s", LoadString("banner.txt").data());
|
2016-07-25 19:37:48 +00:00
|
|
|
#endif
|
Implement a resource system.
Currently, icons, fonts, etc are converted to C structures at compile
time and are hardcoded to the binary. This presents several problems:
* Cross-compilation is complicated. Right now, it is necessary
to be able to run executables for the target platform; this
happens to work with wine-binfmt installed, but is rather ugly.
* Icons can only have one resolution. On OS X, modern software is
expected to take advantage of high-DPI ("Retina") screens and
use so-called @2x assets when ran in high-DPI mode.
* Localization is complicated. Win32 and OS X provide built-in
support for loading the resource appropriate for the user's
locale.
* Embedding strings can only be done as raw strings, using C++'s
R"(...)" literals. This precludes embedding sizable strings,
e.g. JavaScript libraries as used in Three.js export, and makes
git history less useful. Not embedding the libraries means we
have to rely on external CDNs, which requires an Internet
connection and adds a glaring point of failure.
* Linux distribution guidelines are violated. All architecture-
independent data, especially large data such as fonts, is
expected to be in /usr/share, not in the binary.
* Customization is impossible without recompilation. Minor
modifications like adding a few missing vector font characters
or adjusting localization require a complete development
environment, which is unreasonable to expect from users of
a mechanical CAD.
As such, this commit adds a resource system that bundles (and
sometimes builds) resources with the executable. Where they go is
platform-dependent:
* on Win32: into resources of the executable, which allows us to
keep distributing one file;
* on OS X: into the app bundle;
* on other *nix: into /usr/share/solvespace/ or ../res/ (relative
to the executable path), the latter allowing us to run freshly
built executables without installation.
It also subsides the platform-specific resources that are in src/.
The resource system is not yet used for anything; this will be added
in later commits.
2016-04-21 15:54:18 +00:00
|
|
|
|
2010-05-16 16:36:23 +00:00
|
|
|
SS.tangentArcRadius = 10.0;
|
|
|
|
|
2008-02-09 13:52:01 +00:00
|
|
|
// Then, load the registry settings.
|
2008-06-11 04:22:52 +00:00
|
|
|
// Default list of colors for the model material
|
2013-12-02 06:25:09 +00:00
|
|
|
modelColor[0] = CnfThawColor(RGBi(150, 150, 150), "ModelColor_0");
|
|
|
|
modelColor[1] = CnfThawColor(RGBi(100, 100, 100), "ModelColor_1");
|
|
|
|
modelColor[2] = CnfThawColor(RGBi( 30, 30, 30), "ModelColor_2");
|
|
|
|
modelColor[3] = CnfThawColor(RGBi(150, 0, 0), "ModelColor_3");
|
|
|
|
modelColor[4] = CnfThawColor(RGBi( 0, 100, 0), "ModelColor_4");
|
|
|
|
modelColor[5] = CnfThawColor(RGBi( 0, 80, 80), "ModelColor_5");
|
|
|
|
modelColor[6] = CnfThawColor(RGBi( 0, 0, 130), "ModelColor_6");
|
|
|
|
modelColor[7] = CnfThawColor(RGBi( 80, 0, 80), "ModelColor_7");
|
2008-06-11 04:22:52 +00:00
|
|
|
// Light intensities
|
2008-07-08 07:41:29 +00:00
|
|
|
lightIntensity[0] = CnfThawFloat(1.0f, "LightIntensity_0");
|
|
|
|
lightIntensity[1] = CnfThawFloat(0.5f, "LightIntensity_1");
|
2009-03-17 16:33:46 +00:00
|
|
|
ambientIntensity = 0.3; // no setting for that yet
|
2008-06-11 04:22:52 +00:00
|
|
|
// Light positions
|
2008-07-08 07:41:29 +00:00
|
|
|
lightDir[0].x = CnfThawFloat(-1.0f, "LightDir_0_Right" );
|
|
|
|
lightDir[0].y = CnfThawFloat( 1.0f, "LightDir_0_Up" );
|
|
|
|
lightDir[0].z = CnfThawFloat( 0.0f, "LightDir_0_Forward" );
|
|
|
|
lightDir[1].x = CnfThawFloat( 1.0f, "LightDir_1_Right" );
|
|
|
|
lightDir[1].y = CnfThawFloat( 0.0f, "LightDir_1_Up" );
|
|
|
|
lightDir[1].z = CnfThawFloat( 0.0f, "LightDir_1_Forward" );
|
2016-01-27 04:07:54 +00:00
|
|
|
|
|
|
|
exportMode = false;
|
2008-07-10 05:26:08 +00:00
|
|
|
// Chord tolerance
|
Use relative chord tolerance instead of absolute.
Commit 89eb208 has improved the overall situation with chord
tolerance, but it changed the display chord tolerance to use
an absolute value in millimeters as a stopgap measure.
This commit changes the display chord tolerance to be specified
in percents of entity bounding box instead of millimeters.
As a result, the linearized curves are both zoom level and sketch
scale independent.
In order to compute the bounding box, all entities are generated
twice. However, this shouldn't result in a noticeable slowdown,
since the bounding box calculation does not need the expensive
triangle mesh generation and the solver will converge immediately
on the second run.
Since the meaning of the preference has changed, a new name is
used (ChordTolerancePct instead of ChordTolerance), so that it
would be reset to the default value after updating SolveSpace.
The default value, 0.5%, was selected using trial and error by
judging whether cylinders of moderate dimensions were looking
aesthetically pleasing enough.
After this change, the only real function of the spacebar
shortcut is to reload imported groups, since manual regeneration
should not change anything anymore unless there is a bug.
2016-01-29 10:33:56 +00:00
|
|
|
chordTol = CnfThawFloat(0.5f, "ChordTolerancePct");
|
2008-02-12 13:00:26 +00:00
|
|
|
// Max pwl segments to generate
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
maxSegments = CnfThawInt(10, "MaxSegments");
|
2016-01-27 04:07:54 +00:00
|
|
|
// Chord tolerance
|
|
|
|
exportChordTol = CnfThawFloat(0.1f, "ExportChordTolerance");
|
|
|
|
// Max pwl segments to generate
|
|
|
|
exportMaxSegments = CnfThawInt(64, "ExportMaxSegments");
|
2008-06-14 09:51:25 +00:00
|
|
|
// View units
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
viewUnits = (Unit)CnfThawInt((uint32_t)Unit::MM, "ViewUnits");
|
2010-09-24 02:58:34 +00:00
|
|
|
// Number of digits after the decimal point
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
afterDecimalMm = CnfThawInt(2, "AfterDecimalMm");
|
|
|
|
afterDecimalInch = CnfThawInt(3, "AfterDecimalInch");
|
2008-06-17 19:12:25 +00:00
|
|
|
// Camera tangent (determines perspective)
|
2010-05-16 18:46:10 +00:00
|
|
|
cameraTangent = CnfThawFloat(0.3f/1e3f, "CameraTangent");
|
2009-09-29 11:35:19 +00:00
|
|
|
// Grid spacing
|
|
|
|
gridSpacing = CnfThawFloat(5.0f, "GridSpacing");
|
2008-07-08 07:41:29 +00:00
|
|
|
// Export scale factor
|
|
|
|
exportScale = CnfThawFloat(1.0f, "ExportScale");
|
2008-08-14 08:28:25 +00:00
|
|
|
// Export offset (cutter radius comp)
|
|
|
|
exportOffset = CnfThawFloat(0.0f, "ExportOffset");
|
2009-09-22 05:46:30 +00:00
|
|
|
// Rewrite exported colors close to white into black (assuming white bg)
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
fixExportColors = CnfThawBool(true, "FixExportColors");
|
2008-08-11 10:56:08 +00:00
|
|
|
// Draw back faces of triangles (when mesh is leaky/self-intersecting)
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
drawBackFaces = CnfThawBool(true, "DrawBackFaces");
|
2009-10-01 10:35:11 +00:00
|
|
|
// Check that contours are closed and not self-intersecting
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
checkClosedContour = CnfThawBool(true, "CheckClosedContour");
|
2009-03-18 04:26:04 +00:00
|
|
|
// Export shaded triangles in a 2d view
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
exportShadedTriangles = CnfThawBool(true, "ExportShadedTriangles");
|
2009-04-14 04:19:23 +00:00
|
|
|
// Export pwl curves (instead of exact) always
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
exportPwlCurves = CnfThawBool(false, "ExportPwlCurves");
|
2009-09-18 08:14:15 +00:00
|
|
|
// Background color on-screen
|
2013-12-02 06:25:09 +00:00
|
|
|
backgroundColor = CnfThawColor(RGBi(0, 0, 0), "BackgroundColor");
|
2009-09-03 08:13:09 +00:00
|
|
|
// Whether export canvas size is fixed or derived from bbox
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
exportCanvasSizeAuto = CnfThawBool(true, "ExportCanvasSizeAuto");
|
2009-09-03 08:13:09 +00:00
|
|
|
// Margins for automatic canvas size
|
|
|
|
exportMargin.left = CnfThawFloat(5.0f, "ExportMargin_Left");
|
|
|
|
exportMargin.right = CnfThawFloat(5.0f, "ExportMargin_Right");
|
|
|
|
exportMargin.bottom = CnfThawFloat(5.0f, "ExportMargin_Bottom");
|
|
|
|
exportMargin.top = CnfThawFloat(5.0f, "ExportMargin_Top");
|
|
|
|
// Dimensions for fixed canvas size
|
|
|
|
exportCanvas.width = CnfThawFloat(100.0f, "ExportCanvas_Width");
|
|
|
|
exportCanvas.height = CnfThawFloat(100.0f, "ExportCanvas_Height");
|
|
|
|
exportCanvas.dx = CnfThawFloat( 5.0f, "ExportCanvas_Dx");
|
|
|
|
exportCanvas.dy = CnfThawFloat( 5.0f, "ExportCanvas_Dy");
|
2010-01-14 04:47:17 +00:00
|
|
|
// Extra parameters when exporting G code
|
|
|
|
gCode.depth = CnfThawFloat(10.0f, "GCode_Depth");
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
gCode.passes = CnfThawInt(1, "GCode_Passes");
|
2010-01-14 04:47:17 +00:00
|
|
|
gCode.feed = CnfThawFloat(10.0f, "GCode_Feed");
|
|
|
|
gCode.plungeFeed = CnfThawFloat(10.0f, "GCode_PlungeFeed");
|
2009-01-02 10:38:36 +00:00
|
|
|
// Show toolbar in the graphics window
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
showToolbar = CnfThawBool(true, "ShowToolbar");
|
2008-06-11 04:22:52 +00:00
|
|
|
// Recent files menus
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
for(size_t i = 0; i < MAX_RECENT; i++) {
|
2015-12-27 01:03:24 +00:00
|
|
|
RecentFile[i] = CnfThawString("", "RecentFile_" + std::to_string(i));
|
2008-06-11 04:22:52 +00:00
|
|
|
}
|
|
|
|
RefreshRecentMenus();
|
2015-03-29 04:46:57 +00:00
|
|
|
// Autosave timer
|
|
|
|
autosaveInterval = CnfThawInt(5, "AutosaveInterval");
|
2017-01-05 10:39:08 +00:00
|
|
|
// Locale
|
|
|
|
std::string locale = CnfThawString("", "Locale");
|
|
|
|
if(!locale.empty()) {
|
|
|
|
SetLocale(locale);
|
|
|
|
}
|
2008-06-11 04:22:52 +00:00
|
|
|
|
2009-09-17 07:32:36 +00:00
|
|
|
// The default styles (colors, line widths, etc.) are also stored in the
|
|
|
|
// configuration file, but we will automatically load those as we need
|
|
|
|
// them.
|
|
|
|
|
2015-03-29 04:46:57 +00:00
|
|
|
SetAutosaveTimerFor(autosaveInterval);
|
|
|
|
|
2008-05-29 10:10:12 +00:00
|
|
|
NewFile();
|
|
|
|
AfterNewFile();
|
2015-03-24 06:45:53 +00:00
|
|
|
}
|
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
bool SolveSpaceUI::LoadAutosaveFor(const std::string &filename) {
|
|
|
|
std::string autosaveFile = filename + AUTOSAVE_SUFFIX;
|
2015-03-29 04:46:57 +00:00
|
|
|
|
2015-12-27 08:09:00 +00:00
|
|
|
FILE *f = ssfopen(autosaveFile, "rb");
|
2015-03-29 04:46:57 +00:00
|
|
|
if(!f)
|
|
|
|
return false;
|
|
|
|
fclose(f);
|
|
|
|
|
2016-01-11 12:18:18 +00:00
|
|
|
if(LoadAutosaveYesNo() == DIALOG_YES) {
|
2015-03-29 04:46:57 +00:00
|
|
|
unsaved = true;
|
2016-11-28 16:20:59 +00:00
|
|
|
return LoadFromFile(autosaveFile, /*canCancel=*/true);
|
2015-03-29 04:46:57 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
bool SolveSpaceUI::OpenFile(const std::string &filename) {
|
2015-03-29 04:46:57 +00:00
|
|
|
bool autosaveLoaded = LoadAutosaveFor(filename);
|
2016-11-28 16:20:59 +00:00
|
|
|
bool fileLoaded = autosaveLoaded || LoadFromFile(filename, /*canCancel=*/true);
|
|
|
|
if(fileLoaded) {
|
2016-01-11 12:18:18 +00:00
|
|
|
saveFile = filename;
|
2015-03-24 06:45:53 +00:00
|
|
|
AddToRecentList(filename);
|
|
|
|
} else {
|
2016-01-11 12:18:18 +00:00
|
|
|
saveFile = "";
|
2015-03-24 06:45:53 +00:00
|
|
|
NewFile();
|
2008-04-24 06:22:16 +00:00
|
|
|
}
|
2008-05-28 10:10:31 +00:00
|
|
|
AfterNewFile();
|
2015-03-29 04:46:57 +00:00
|
|
|
unsaved = autosaveLoaded;
|
2016-11-28 16:20:59 +00:00
|
|
|
return fileLoaded;
|
2008-05-28 10:10:31 +00:00
|
|
|
}
|
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
void SolveSpaceUI::Exit() {
|
2008-06-11 04:22:52 +00:00
|
|
|
// Recent files
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
for(size_t i = 0; i < MAX_RECENT; i++)
|
2015-12-27 01:03:24 +00:00
|
|
|
CnfFreezeString(RecentFile[i], "RecentFile_" + std::to_string(i));
|
2008-06-11 04:22:52 +00:00
|
|
|
// Model colors
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
for(size_t i = 0; i < MODEL_COLORS; i++)
|
2015-12-27 01:03:24 +00:00
|
|
|
CnfFreezeColor(modelColor[i], "ModelColor_" + std::to_string(i));
|
2008-06-11 04:22:52 +00:00
|
|
|
// Light intensities
|
2008-07-08 07:41:29 +00:00
|
|
|
CnfFreezeFloat((float)lightIntensity[0], "LightIntensity_0");
|
|
|
|
CnfFreezeFloat((float)lightIntensity[1], "LightIntensity_1");
|
2008-06-11 04:30:18 +00:00
|
|
|
// Light directions
|
2008-07-08 07:41:29 +00:00
|
|
|
CnfFreezeFloat((float)lightDir[0].x, "LightDir_0_Right");
|
|
|
|
CnfFreezeFloat((float)lightDir[0].y, "LightDir_0_Up");
|
|
|
|
CnfFreezeFloat((float)lightDir[0].z, "LightDir_0_Forward");
|
|
|
|
CnfFreezeFloat((float)lightDir[1].x, "LightDir_1_Right");
|
|
|
|
CnfFreezeFloat((float)lightDir[1].y, "LightDir_1_Up");
|
|
|
|
CnfFreezeFloat((float)lightDir[1].z, "LightDir_1_Forward");
|
2008-07-10 05:26:08 +00:00
|
|
|
// Chord tolerance
|
Use relative chord tolerance instead of absolute.
Commit 89eb208 has improved the overall situation with chord
tolerance, but it changed the display chord tolerance to use
an absolute value in millimeters as a stopgap measure.
This commit changes the display chord tolerance to be specified
in percents of entity bounding box instead of millimeters.
As a result, the linearized curves are both zoom level and sketch
scale independent.
In order to compute the bounding box, all entities are generated
twice. However, this shouldn't result in a noticeable slowdown,
since the bounding box calculation does not need the expensive
triangle mesh generation and the solver will converge immediately
on the second run.
Since the meaning of the preference has changed, a new name is
used (ChordTolerancePct instead of ChordTolerance), so that it
would be reset to the default value after updating SolveSpace.
The default value, 0.5%, was selected using trial and error by
judging whether cylinders of moderate dimensions were looking
aesthetically pleasing enough.
After this change, the only real function of the spacebar
shortcut is to reload imported groups, since manual regeneration
should not change anything anymore unless there is a bug.
2016-01-29 10:33:56 +00:00
|
|
|
CnfFreezeFloat((float)chordTol, "ChordTolerancePct");
|
2008-02-12 13:00:26 +00:00
|
|
|
// Max pwl segments to generate
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeInt((uint32_t)maxSegments, "MaxSegments");
|
2016-01-27 04:07:54 +00:00
|
|
|
// Export Chord tolerance
|
|
|
|
CnfFreezeFloat((float)exportChordTol, "ExportChordTolerance");
|
|
|
|
// Export Max pwl segments to generate
|
|
|
|
CnfFreezeInt((uint32_t)exportMaxSegments, "ExportMaxSegments");
|
2010-09-24 02:58:34 +00:00
|
|
|
// View units
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeInt((uint32_t)viewUnits, "ViewUnits");
|
2010-09-24 02:58:34 +00:00
|
|
|
// Number of digits after the decimal point
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeInt((uint32_t)afterDecimalMm, "AfterDecimalMm");
|
|
|
|
CnfFreezeInt((uint32_t)afterDecimalInch, "AfterDecimalInch");
|
2008-06-17 19:12:25 +00:00
|
|
|
// Camera tangent (determines perspective)
|
2008-07-08 07:41:29 +00:00
|
|
|
CnfFreezeFloat((float)cameraTangent, "CameraTangent");
|
2009-09-29 11:35:19 +00:00
|
|
|
// Grid spacing
|
|
|
|
CnfFreezeFloat(gridSpacing, "GridSpacing");
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
// Export scale
|
2008-07-08 07:41:29 +00:00
|
|
|
CnfFreezeFloat(exportScale, "ExportScale");
|
2008-08-14 08:28:25 +00:00
|
|
|
// Export offset (cutter radius comp)
|
|
|
|
CnfFreezeFloat(exportOffset, "ExportOffset");
|
2009-09-22 05:46:30 +00:00
|
|
|
// Rewrite exported colors close to white into black (assuming white bg)
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(fixExportColors, "FixExportColors");
|
2008-08-11 10:56:08 +00:00
|
|
|
// Draw back faces of triangles (when mesh is leaky/self-intersecting)
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(drawBackFaces, "DrawBackFaces");
|
2009-10-01 10:35:11 +00:00
|
|
|
// Check that contours are closed and not self-intersecting
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(checkClosedContour, "CheckClosedContour");
|
2009-03-18 04:26:04 +00:00
|
|
|
// Export shaded triangles in a 2d view
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(exportShadedTriangles, "ExportShadedTriangles");
|
2009-04-14 04:19:23 +00:00
|
|
|
// Export pwl curves (instead of exact) always
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(exportPwlCurves, "ExportPwlCurves");
|
2009-09-18 08:14:15 +00:00
|
|
|
// Background color on-screen
|
Replaced RGB-color integers with dedicated data structure
RGB colors were represented using a uint32_t with the red, green and blue
values stuffed into the lower three octets (i.e. 0x00BBGGRR), like
Microsoft's COLORREF. This approach did not lend itself to type safety,
however, so this change replaces it with an RgbColor class that provides
the same infomation plus a handful of useful methods to work with it. (Note
that sizeof(RgbColor) == sizeof(uint32_t), so this change should not lead
to memory bloat.)
Some of the new methods/fields replace what were previously macro calls;
e.g. RED(c) is now c.red, REDf(c) is now c.redF(). The .Equals() method is
now used instead of == to compare colors.
RGB colors still need to be represented as packed integers in file I/O and
preferences, so the methods .FromPackedInt() and .ToPackedInt() are
provided. Also implemented are Cnf{Freeze,Thaw}Color(), type-safe wrappers
around Cnf{Freeze,Thaw}Int() that facilitate I/O with preferences.
(Cnf{Freeze,Thaw}Color() are defined outside of the system-dependent code
to minimize the footprint of the latter; because the same can be done with
Cnf{Freeze,Thaw}Bool(), those are also moved out of the system code with
this commit.)
Color integers were being OR'ed with 0x80000000 in some places for two
distinct purposes: One, to indicate use of a default color in
glxFillMesh(); this has been replaced by use of the .UseDefault() method.
Two, to indicate to TextWindow::Printf() that the format argument of a
"%Bp"/"%Fp" specifier is an RGB color rather than a color "code" from
TextWindow::bgColors[] or TextWindow::fgColors[] (as the specifier can
accept either); instead, we define a new flag "z" (as in "%Bz" or "%Fz") to
indicate an RGBcolor pointer, leaving "%Bp"/"%Fp" to indicate a color code
exclusively.
(This also allows TextWindow::meta[][].bg to be a char instead of an int,
partly compensating for the new .bgRgb field added immediately after.)
In array declarations, RGB colors could previously be specified as 0 (often
in a terminating element). As that no longer works, we define NULL_COLOR,
which serves much the same purpose for RgbColor variables as NULL serves
for pointers.
2013-10-16 20:00:58 +00:00
|
|
|
CnfFreezeColor(backgroundColor, "BackgroundColor");
|
2009-09-03 08:13:09 +00:00
|
|
|
// Whether export canvas size is fixed or derived from bbox
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(exportCanvasSizeAuto, "ExportCanvasSizeAuto");
|
2009-09-03 08:13:09 +00:00
|
|
|
// Margins for automatic canvas size
|
|
|
|
CnfFreezeFloat(exportMargin.left, "ExportMargin_Left");
|
|
|
|
CnfFreezeFloat(exportMargin.right, "ExportMargin_Right");
|
|
|
|
CnfFreezeFloat(exportMargin.bottom, "ExportMargin_Bottom");
|
|
|
|
CnfFreezeFloat(exportMargin.top, "ExportMargin_Top");
|
|
|
|
// Dimensions for fixed canvas size
|
|
|
|
CnfFreezeFloat(exportCanvas.width, "ExportCanvas_Width");
|
|
|
|
CnfFreezeFloat(exportCanvas.height, "ExportCanvas_Height");
|
|
|
|
CnfFreezeFloat(exportCanvas.dx, "ExportCanvas_Dx");
|
|
|
|
CnfFreezeFloat(exportCanvas.dy, "ExportCanvas_Dy");
|
2010-01-14 04:47:17 +00:00
|
|
|
// Extra parameters when exporting G code
|
|
|
|
CnfFreezeFloat(gCode.depth, "GCode_Depth");
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeInt(gCode.passes, "GCode_Passes");
|
2010-01-14 04:47:17 +00:00
|
|
|
CnfFreezeFloat(gCode.feed, "GCode_Feed");
|
|
|
|
CnfFreezeFloat(gCode.plungeFeed, "GCode_PlungeFeed");
|
2009-01-02 10:38:36 +00:00
|
|
|
// Show toolbar in the graphics window
|
Use C99 integer types and C++ boolean types/values
This change comprehensively replaces the use of Microsoft-standard integer
and boolean types with their C99/C++ standard equivalents, as the latter is
more appropriate for a cross-platform application. With matter-of-course
exceptions in the Win32-specific code, the types/values have been converted
as follows:
QWORD --> uint64_t
SQWORD --> int64_t
DWORD --> uint32_t
SDWORD --> int32_t
WORD --> uint16_t
SWORD --> int16_t
BYTE --> uint8_t
BOOL --> bool
TRUE --> true
FALSE --> false
The following related changes are also included:
* Added C99 integer type definitions for Windows, as stdint.h is not
available prior to Visual Studio 2010
* Changed types of some variables in the SolveSpace class from 'int' to
'bool', as they actually represent boolean settings
* Implemented new Cnf{Freeze,Thaw}Bool() functions to support boolean
variables in the Registry
* Cnf{Freeze,Thaw}DWORD() are now Cnf{Freeze,Thaw}Int()
* TtfFont::Get{WORD,DWORD}() are now TtfFont::Get{USHORT,ULONG}() (names
inspired by the OpenType spec)
* RGB colors are packed into an integer of type uint32_t (nee DWORD), but
in a few places, these were represented by an int; these have been
corrected to uint32_t
2013-10-02 05:45:13 +00:00
|
|
|
CnfFreezeBool(showToolbar, "ShowToolbar");
|
2015-03-29 04:46:57 +00:00
|
|
|
// Autosave timer
|
|
|
|
CnfFreezeInt(autosaveInterval, "AutosaveInterval");
|
2008-07-08 07:41:29 +00:00
|
|
|
|
2009-09-17 07:32:36 +00:00
|
|
|
// And the default styles, colors and line widths and such.
|
|
|
|
Style::FreezeDefaultStyles();
|
|
|
|
|
2008-06-11 04:22:52 +00:00
|
|
|
ExitNow();
|
|
|
|
}
|
|
|
|
|
2015-03-23 17:49:04 +00:00
|
|
|
void SolveSpaceUI::ScheduleGenerateAll() {
|
2015-03-18 17:02:11 +00:00
|
|
|
if(!later.scheduled) ScheduleLater();
|
|
|
|
later.scheduled = true;
|
|
|
|
later.generateAll = true;
|
|
|
|
}
|
|
|
|
|
2015-03-23 17:49:04 +00:00
|
|
|
void SolveSpaceUI::ScheduleShowTW() {
|
2015-03-18 17:02:11 +00:00
|
|
|
if(!later.scheduled) ScheduleLater();
|
|
|
|
later.scheduled = true;
|
|
|
|
later.showTW = true;
|
|
|
|
}
|
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
void SolveSpaceUI::DoLater() {
|
2008-06-03 18:28:41 +00:00
|
|
|
if(later.generateAll) GenerateAll();
|
|
|
|
if(later.showTW) TW.Show();
|
2015-03-27 15:31:23 +00:00
|
|
|
later = {};
|
2008-06-03 18:28:41 +00:00
|
|
|
}
|
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
double SolveSpaceUI::MmPerUnit() {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
if(viewUnits == Unit::INCHES) {
|
2010-01-04 00:35:28 +00:00
|
|
|
return 25.4;
|
|
|
|
} else {
|
|
|
|
return 1.0;
|
|
|
|
}
|
|
|
|
}
|
2016-05-05 05:54:05 +00:00
|
|
|
const char *SolveSpaceUI::UnitName() {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
if(viewUnits == Unit::INCHES) {
|
2010-01-04 00:35:28 +00:00
|
|
|
return "inch";
|
|
|
|
} else {
|
|
|
|
return "mm";
|
|
|
|
}
|
|
|
|
}
|
2015-11-06 08:40:12 +00:00
|
|
|
std::string SolveSpaceUI::MmToString(double v) {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
if(viewUnits == Unit::INCHES) {
|
2015-11-06 08:40:12 +00:00
|
|
|
return ssprintf("%.*f", afterDecimalInch, v/25.4);
|
2008-06-14 09:51:25 +00:00
|
|
|
} else {
|
2015-11-06 08:40:12 +00:00
|
|
|
return ssprintf("%.*f", afterDecimalMm, v);
|
2008-06-14 09:51:25 +00:00
|
|
|
}
|
|
|
|
}
|
2015-03-23 17:49:04 +00:00
|
|
|
double SolveSpaceUI::ExprToMm(Expr *e) {
|
2010-01-04 00:35:28 +00:00
|
|
|
return (e->Eval()) * MmPerUnit();
|
2008-06-14 09:51:25 +00:00
|
|
|
}
|
2015-11-06 08:40:12 +00:00
|
|
|
double SolveSpaceUI::StringToMm(const std::string &str) {
|
|
|
|
return std::stod(str) * MmPerUnit();
|
2008-07-20 11:27:22 +00:00
|
|
|
}
|
2016-05-05 05:54:05 +00:00
|
|
|
double SolveSpaceUI::ChordTolMm() {
|
2016-01-27 04:07:54 +00:00
|
|
|
if(exportMode) return ExportChordTolMm();
|
Use relative chord tolerance instead of absolute.
Commit 89eb208 has improved the overall situation with chord
tolerance, but it changed the display chord tolerance to use
an absolute value in millimeters as a stopgap measure.
This commit changes the display chord tolerance to be specified
in percents of entity bounding box instead of millimeters.
As a result, the linearized curves are both zoom level and sketch
scale independent.
In order to compute the bounding box, all entities are generated
twice. However, this shouldn't result in a noticeable slowdown,
since the bounding box calculation does not need the expensive
triangle mesh generation and the solver will converge immediately
on the second run.
Since the meaning of the preference has changed, a new name is
used (ChordTolerancePct instead of ChordTolerance), so that it
would be reset to the default value after updating SolveSpace.
The default value, 0.5%, was selected using trial and error by
judging whether cylinders of moderate dimensions were looking
aesthetically pleasing enough.
After this change, the only real function of the spacebar
shortcut is to reload imported groups, since manual regeneration
should not change anything anymore unless there is a bug.
2016-01-29 10:33:56 +00:00
|
|
|
return chordTolCalculated;
|
2016-01-27 04:07:54 +00:00
|
|
|
}
|
2016-05-05 05:54:05 +00:00
|
|
|
double SolveSpaceUI::ExportChordTolMm() {
|
2016-01-27 04:07:54 +00:00
|
|
|
return exportChordTol / exportScale;
|
|
|
|
}
|
2016-05-05 05:54:05 +00:00
|
|
|
int SolveSpaceUI::GetMaxSegments() {
|
2016-01-27 04:07:54 +00:00
|
|
|
if(exportMode) return exportMaxSegments;
|
|
|
|
return maxSegments;
|
2009-03-08 10:59:57 +00:00
|
|
|
}
|
2016-05-05 05:54:05 +00:00
|
|
|
int SolveSpaceUI::UnitDigitsAfterDecimal() {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
return (viewUnits == Unit::INCHES) ? afterDecimalInch : afterDecimalMm;
|
2010-09-24 02:58:34 +00:00
|
|
|
}
|
2015-03-23 17:49:04 +00:00
|
|
|
void SolveSpaceUI::SetUnitDigitsAfterDecimal(int v) {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
if(viewUnits == Unit::INCHES) {
|
2010-09-24 02:58:34 +00:00
|
|
|
afterDecimalInch = v;
|
|
|
|
} else {
|
|
|
|
afterDecimalMm = v;
|
|
|
|
}
|
|
|
|
}
|
2008-06-14 09:51:25 +00:00
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
double SolveSpaceUI::CameraTangent() {
|
2010-05-03 05:15:28 +00:00
|
|
|
if(!usePerspectiveProj) {
|
2009-09-29 11:35:19 +00:00
|
|
|
return 0;
|
|
|
|
} else {
|
|
|
|
return cameraTangent;
|
|
|
|
}
|
|
|
|
}
|
2008-06-14 09:51:25 +00:00
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
void SolveSpaceUI::AfterNewFile() {
|
2008-07-20 11:27:22 +00:00
|
|
|
// Clear out the traced point, which is no longer valid
|
|
|
|
traced.point = Entity::NO_ENTITY;
|
|
|
|
traced.path.l.Clear();
|
2009-01-25 09:19:59 +00:00
|
|
|
// and the naked edges
|
|
|
|
nakedEdges.Clear();
|
2008-07-20 11:27:22 +00:00
|
|
|
|
2016-04-16 09:05:12 +00:00
|
|
|
// Quit export mode
|
|
|
|
justExportedInfo.draw = false;
|
|
|
|
exportMode = false;
|
|
|
|
|
2009-06-04 03:59:40 +00:00
|
|
|
// GenerateAll() expects the view to be valid, because it uses that to
|
|
|
|
// fill in default values for extrusion depths etc. (which won't matter
|
|
|
|
// here, but just don't let it work on garbage)
|
|
|
|
SS.GW.offset = Vector::From(0, 0, 0);
|
|
|
|
SS.GW.projRight = Vector::From(1, 0, 0);
|
|
|
|
SS.GW.projUp = Vector::From(0, 1, 0);
|
|
|
|
|
2016-10-12 23:15:15 +00:00
|
|
|
GenerateAll(Generate::ALL);
|
2008-05-25 13:11:44 +00:00
|
|
|
|
2008-04-13 10:57:41 +00:00
|
|
|
TW.Init();
|
|
|
|
GW.Init();
|
|
|
|
|
2008-06-03 18:28:41 +00:00
|
|
|
unsaved = false;
|
2008-06-12 07:31:41 +00:00
|
|
|
|
|
|
|
int w, h;
|
|
|
|
GetGraphicsWindowSize(&w, &h);
|
|
|
|
GW.width = w;
|
|
|
|
GW.height = h;
|
2008-06-21 10:18:20 +00:00
|
|
|
|
2016-05-25 12:08:19 +00:00
|
|
|
GW.ZoomToFit(/*includingInvisibles=*/false);
|
2008-07-08 08:02:22 +00:00
|
|
|
|
2009-09-18 08:14:15 +00:00
|
|
|
// Create all the default styles; they'll get created on the fly anyways,
|
|
|
|
// but can't hurt to do it now.
|
|
|
|
Style::CreateAllDefaultStyles();
|
|
|
|
|
2008-07-08 08:02:22 +00:00
|
|
|
UpdateWindowTitle();
|
2008-04-08 12:54:53 +00:00
|
|
|
}
|
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
void SolveSpaceUI::RemoveFromRecentList(const std::string &filename) {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
int dest = 0;
|
|
|
|
for(int src = 0; src < (int)MAX_RECENT; src++) {
|
2015-12-27 01:03:24 +00:00
|
|
|
if(filename != RecentFile[src]) {
|
|
|
|
if(src != dest) RecentFile[dest] = RecentFile[src];
|
2008-05-28 10:10:31 +00:00
|
|
|
dest++;
|
|
|
|
}
|
|
|
|
}
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
while(dest < (int)MAX_RECENT) RecentFile[dest++].clear();
|
2008-05-28 10:10:31 +00:00
|
|
|
RefreshRecentMenus();
|
|
|
|
}
|
2015-12-27 01:03:24 +00:00
|
|
|
void SolveSpaceUI::AddToRecentList(const std::string &filename) {
|
|
|
|
RemoveFromRecentList(filename);
|
2008-05-28 10:10:31 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
for(int src = MAX_RECENT - 2; src >= 0; src--) {
|
2015-12-27 01:03:24 +00:00
|
|
|
RecentFile[src+1] = RecentFile[src];
|
2008-05-28 10:10:31 +00:00
|
|
|
}
|
2015-12-27 01:03:24 +00:00
|
|
|
RecentFile[0] = filename;
|
2008-05-28 10:10:31 +00:00
|
|
|
RefreshRecentMenus();
|
|
|
|
}
|
|
|
|
|
2015-03-23 17:49:04 +00:00
|
|
|
bool SolveSpaceUI::GetFilenameAndSave(bool saveAs) {
|
2015-12-27 01:03:24 +00:00
|
|
|
std::string prevSaveFile = saveFile;
|
2009-06-10 06:57:27 +00:00
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
if(saveAs || saveFile.empty()) {
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&saveFile, "", SlvsFileFilter)) return false;
|
2015-05-21 12:26:29 +00:00
|
|
|
// need to get new filename directly into saveFile, since that
|
2016-05-07 05:27:54 +00:00
|
|
|
// determines linkFileRel path
|
2008-06-03 18:28:41 +00:00
|
|
|
}
|
|
|
|
|
2015-05-21 12:26:29 +00:00
|
|
|
if(SaveToFile(saveFile)) {
|
|
|
|
AddToRecentList(saveFile);
|
2015-03-29 04:46:57 +00:00
|
|
|
RemoveAutosave();
|
2008-06-03 18:28:41 +00:00
|
|
|
unsaved = false;
|
|
|
|
return true;
|
|
|
|
} else {
|
2015-05-21 12:26:29 +00:00
|
|
|
// don't store an invalid save filename
|
2015-12-27 01:03:24 +00:00
|
|
|
saveFile = prevSaveFile;
|
2008-06-03 18:28:41 +00:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-03-29 04:46:57 +00:00
|
|
|
bool SolveSpaceUI::Autosave()
|
|
|
|
{
|
|
|
|
SetAutosaveTimerFor(autosaveInterval);
|
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
if(!saveFile.empty() && unsaved)
|
|
|
|
return SaveToFile(saveFile + AUTOSAVE_SUFFIX);
|
2015-03-29 04:46:57 +00:00
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
void SolveSpaceUI::RemoveAutosave()
|
|
|
|
{
|
2015-12-27 01:03:24 +00:00
|
|
|
std::string autosaveFile = saveFile + AUTOSAVE_SUFFIX;
|
2016-02-14 20:13:40 +00:00
|
|
|
ssremove(autosaveFile);
|
2015-03-29 04:46:57 +00:00
|
|
|
}
|
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
bool SolveSpaceUI::OkayToStartNewFile() {
|
2008-06-03 18:28:41 +00:00
|
|
|
if(!unsaved) return true;
|
|
|
|
|
|
|
|
switch(SaveFileYesNoCancel()) {
|
2016-01-11 12:18:18 +00:00
|
|
|
case DIALOG_YES:
|
2016-05-25 12:08:19 +00:00
|
|
|
return GetFilenameAndSave(/*saveAs=*/false);
|
2008-06-03 18:28:41 +00:00
|
|
|
|
2016-01-11 12:18:18 +00:00
|
|
|
case DIALOG_NO:
|
2016-06-23 02:50:25 +00:00
|
|
|
RemoveAutosave();
|
2008-06-03 18:28:41 +00:00
|
|
|
return true;
|
|
|
|
|
2016-01-11 12:18:18 +00:00
|
|
|
case DIALOG_CANCEL:
|
2008-06-03 18:28:41 +00:00
|
|
|
return false;
|
|
|
|
}
|
Enable exhaustive switch coverage warnings as an error, and use them.
Specifically, this enables -Wswitch=error on GCC/Clang and its MSVC
equivalent; the exact way it is handled varies slightly, but what
they all have in common is that in a switch statement over an
enumeration, any enumerand that is not explicitly (via case:) or
implicitly (via default:) handled in the switch triggers an error.
Moreover, we also change the switch statements in three ways:
* Switch statements that ought to be extended every time a new
enumerand is added (e.g. Entity::DrawOrGetDistance(), are changed
to explicitly list every single enumerand, and not have a
default: branch.
Note that the assertions are kept because it is legal for
a enumeration to have a value unlike any of its defined
enumerands, and we can e.g. read garbage from a file, or
an uninitialized variable. This requires some rearranging if
a default: branch is undesired.
* Switch statements that ought to only ever see a few select
enumerands, are changed to always assert in the default: branch.
* Switch statements that do something meaningful for a few
enumerands, and ignore everything else, are changed to do nothing
in a default: branch, under the assumption that changing them
every time an enumerand is added or removed would just result
in noise and catch no bugs.
This commit also removes the {Request,Entity,Constraint}::UNKNOWN and
Entity::DATUM_POINT enumerands, as those were just fancy names for
zeroes. They mess up switch exhaustiveness checks and most of the time
were not the best way to implement what they did anyway.
2016-05-25 06:55:50 +00:00
|
|
|
ssassert(false, "Unexpected dialog choice");
|
2008-06-03 18:28:41 +00:00
|
|
|
}
|
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
void SolveSpaceUI::UpdateWindowTitle() {
|
2015-12-27 01:03:24 +00:00
|
|
|
SetCurrentFilename(saveFile);
|
2008-07-08 08:02:22 +00:00
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
void SolveSpaceUI::MenuFile(Command id) {
|
|
|
|
if((uint32_t)id >= (uint32_t)Command::RECENT_OPEN &&
|
|
|
|
(uint32_t)id < ((uint32_t)Command::RECENT_OPEN+MAX_RECENT)) {
|
2008-07-10 06:11:56 +00:00
|
|
|
if(!SS.OkayToStartNewFile()) return;
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
std::string newFile = RecentFile[(uint32_t)id - (uint32_t)Command::RECENT_OPEN];
|
2015-03-29 04:46:57 +00:00
|
|
|
SS.OpenFile(newFile);
|
2008-05-28 10:10:31 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2008-04-18 11:11:48 +00:00
|
|
|
switch(id) {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::NEW:
|
2008-06-03 18:28:41 +00:00
|
|
|
if(!SS.OkayToStartNewFile()) break;
|
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
SS.saveFile = "";
|
2008-04-24 06:22:16 +00:00
|
|
|
SS.NewFile();
|
2008-05-28 10:10:31 +00:00
|
|
|
SS.AfterNewFile();
|
2008-04-24 06:22:16 +00:00
|
|
|
break;
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::OPEN: {
|
2008-06-03 18:28:41 +00:00
|
|
|
if(!SS.OkayToStartNewFile()) break;
|
|
|
|
|
2015-12-27 01:03:24 +00:00
|
|
|
std::string newFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(GetOpenFile(&newFile, "", SlvsFileFilter)) {
|
2015-03-29 04:46:57 +00:00
|
|
|
SS.OpenFile(newFile);
|
2008-05-28 10:10:31 +00:00
|
|
|
}
|
2008-04-24 06:22:16 +00:00
|
|
|
break;
|
2008-05-28 10:10:31 +00:00
|
|
|
}
|
2008-04-18 11:11:48 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::SAVE:
|
2016-05-25 12:08:19 +00:00
|
|
|
SS.GetFilenameAndSave(/*saveAs=*/false);
|
2008-06-03 18:28:41 +00:00
|
|
|
break;
|
2008-04-18 11:11:48 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::SAVE_AS:
|
2016-05-25 12:08:19 +00:00
|
|
|
SS.GetFilenameAndSave(/*saveAs=*/true);
|
2008-04-18 11:11:48 +00:00
|
|
|
break;
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXPORT_PNG: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&exportFile, "", PngFileFilter)) break;
|
2015-03-29 00:30:52 +00:00
|
|
|
SS.ExportAsPngTo(exportFile);
|
2008-06-18 08:35:14 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXPORT_VIEW: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&exportFile, CnfThawString("", "ViewExportFormat"),
|
|
|
|
VectorFileFilter)) break;
|
2016-01-11 08:23:51 +00:00
|
|
|
CnfFreezeString(Extension(exportFile), "ViewExportFormat");
|
2010-01-14 04:47:17 +00:00
|
|
|
|
|
|
|
// If the user is exporting something where it would be
|
|
|
|
// inappropriate to include the constraints, then warn.
|
|
|
|
if(SS.GW.showConstraints &&
|
2015-12-27 01:03:24 +00:00
|
|
|
(FilenameHasExtension(exportFile, ".txt") ||
|
2010-01-14 04:47:17 +00:00
|
|
|
fabs(SS.exportOffset) > LENGTH_EPS))
|
|
|
|
{
|
|
|
|
Message("Constraints are currently shown, and will be exported "
|
|
|
|
"in the toolpath. This is probably not what you want; "
|
|
|
|
"hide them by clicking the link at the top of the "
|
|
|
|
"text window.");
|
|
|
|
}
|
|
|
|
|
2016-05-25 12:08:19 +00:00
|
|
|
SS.ExportViewOrWireframeTo(exportFile, /*exportWireframe*/false);
|
2009-10-12 10:40:48 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXPORT_WIREFRAME: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&exportFile, CnfThawString("", "WireframeExportFormat"),
|
|
|
|
Vector3dFileFilter)) break;
|
2016-01-11 08:23:51 +00:00
|
|
|
CnfFreezeString(Extension(exportFile), "WireframeExportFormat");
|
|
|
|
|
2016-05-25 12:08:19 +00:00
|
|
|
SS.ExportViewOrWireframeTo(exportFile, /*exportWireframe*/true);
|
2009-01-14 05:10:42 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXPORT_SECTION: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&exportFile, CnfThawString("", "SectionExportFormat"),
|
|
|
|
VectorFileFilter)) break;
|
2016-01-11 08:23:51 +00:00
|
|
|
CnfFreezeString(Extension(exportFile), "SectionExportFormat");
|
|
|
|
|
2015-03-29 00:30:52 +00:00
|
|
|
SS.ExportSectionTo(exportFile);
|
2008-07-08 06:30:13 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXPORT_MESH: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&exportFile, CnfThawString("", "MeshExportFormat"),
|
|
|
|
MeshFileFilter)) break;
|
2016-01-11 08:23:51 +00:00
|
|
|
CnfFreezeString(Extension(exportFile), "MeshExportFormat");
|
|
|
|
|
2015-03-29 00:30:52 +00:00
|
|
|
SS.ExportMeshTo(exportFile);
|
2008-07-06 09:24:31 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXPORT_SURFACES: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(!GetSaveFile(&exportFile, CnfThawString("", "SurfacesExportFormat"),
|
|
|
|
SurfaceFileFilter)) break;
|
2016-01-11 08:23:51 +00:00
|
|
|
CnfFreezeString(Extension(exportFile), "SurfacesExportFormat");
|
|
|
|
|
2015-03-27 15:31:23 +00:00
|
|
|
StepFileWriter sfw = {};
|
2015-03-29 00:30:52 +00:00
|
|
|
sfw.ExportSurfacesTo(exportFile);
|
2009-06-08 06:50:16 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::IMPORT: {
|
2016-04-13 08:43:06 +00:00
|
|
|
std::string importFile;
|
|
|
|
if(!GetOpenFile(&importFile, CnfThawString("", "ImportFormat"),
|
|
|
|
ImportableFileFilter)) break;
|
|
|
|
CnfFreezeString(Extension(importFile), "ImportFormat");
|
|
|
|
|
2016-05-07 05:17:23 +00:00
|
|
|
if(Extension(importFile) == "dxf") {
|
|
|
|
ImportDxf(importFile);
|
|
|
|
} else if(Extension(importFile) == "dwg") {
|
|
|
|
ImportDwg(importFile);
|
2016-11-17 05:24:02 +00:00
|
|
|
} else {
|
|
|
|
Error("Can't identify file type from file extension of "
|
|
|
|
"filename '%s'; try .dxf or .dwg.", importFile.c_str());
|
|
|
|
}
|
2016-05-09 12:43:52 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
SS.GenerateAll(SolveSpaceUI::Generate::UNTIL_ACTIVE);
|
2016-05-09 12:43:52 +00:00
|
|
|
SS.ScheduleShowTW();
|
2016-04-13 08:43:06 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::EXIT:
|
2008-06-03 18:28:41 +00:00
|
|
|
if(!SS.OkayToStartNewFile()) break;
|
2008-06-11 04:22:52 +00:00
|
|
|
SS.Exit();
|
2008-04-18 11:11:48 +00:00
|
|
|
break;
|
|
|
|
|
2016-05-18 22:51:36 +00:00
|
|
|
default: ssassert(false, "Unexpected menu ID");
|
2008-04-18 11:11:48 +00:00
|
|
|
}
|
2008-07-08 08:02:22 +00:00
|
|
|
|
|
|
|
SS.UpdateWindowTitle();
|
2008-04-18 11:11:48 +00:00
|
|
|
}
|
2008-07-20 11:27:22 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
void SolveSpaceUI::MenuAnalyze(Command id) {
|
2008-07-20 11:27:22 +00:00
|
|
|
SS.GW.GroupSelection();
|
2016-10-10 12:34:10 +00:00
|
|
|
auto const &gs = SS.GW.gs;
|
2008-07-20 11:27:22 +00:00
|
|
|
|
|
|
|
switch(id) {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::STEP_DIM:
|
2008-07-20 11:27:22 +00:00
|
|
|
if(gs.constraints == 1 && gs.n == 0) {
|
2009-04-19 05:53:16 +00:00
|
|
|
Constraint *c = SK.GetConstraint(gs.constraint[0]);
|
2008-07-20 11:27:22 +00:00
|
|
|
if(c->HasLabel() && !c->reference) {
|
|
|
|
SS.TW.shown.dimFinish = c->valA;
|
|
|
|
SS.TW.shown.dimSteps = 10;
|
|
|
|
SS.TW.shown.dimIsDistance =
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
(c->type != Constraint::Type::ANGLE) &&
|
|
|
|
(c->type != Constraint::Type::LENGTH_RATIO) &&
|
|
|
|
(c->type != Constraint::Type::LENGTH_DIFFERENCE);
|
2008-07-20 11:27:22 +00:00
|
|
|
SS.TW.shown.constraint = c->h;
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
SS.TW.shown.screen = TextWindow::Screen::STEP_DIMENSION;
|
2008-07-20 11:27:22 +00:00
|
|
|
|
2008-09-17 10:13:37 +00:00
|
|
|
// The step params are specified in the text window,
|
|
|
|
// so force that to be shown.
|
|
|
|
SS.GW.ForceTextWindowShown();
|
|
|
|
|
2015-03-18 17:02:11 +00:00
|
|
|
SS.ScheduleShowTW();
|
2008-07-20 11:27:22 +00:00
|
|
|
SS.GW.ClearSelection();
|
|
|
|
} else {
|
|
|
|
Error("Constraint must have a label, and must not be "
|
|
|
|
"a reference dimension.");
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
Error("Bad selection for step dimension; select a constraint.");
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::NAKED_EDGES: {
|
2016-11-14 15:16:50 +00:00
|
|
|
ShowNakedEdges(/*reportOnlyWhenNotOkay=*/false);
|
2009-01-19 10:37:10 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::INTERFERENCE: {
|
2009-05-22 10:02:02 +00:00
|
|
|
SS.nakedEdges.Clear();
|
|
|
|
|
|
|
|
SMesh *m = &(SK.GetGroup(SS.GW.activeGroup)->displayMesh);
|
|
|
|
SKdNode *root = SKdNode::From(m);
|
|
|
|
bool inters, leaks;
|
2009-05-29 05:40:17 +00:00
|
|
|
root->MakeCertainEdgesInto(&(SS.nakedEdges),
|
2016-05-25 12:08:19 +00:00
|
|
|
EdgeKind::SELF_INTER, /*coplanarIsInter=*/false, &inters, &leaks);
|
2009-05-29 05:40:17 +00:00
|
|
|
|
2009-05-22 10:02:02 +00:00
|
|
|
InvalidateGraphics();
|
|
|
|
|
|
|
|
if(inters) {
|
|
|
|
Error("%d edges interfere with other triangles, bad.",
|
|
|
|
SS.nakedEdges.l.n);
|
|
|
|
} else {
|
|
|
|
Message("The assembly does not interfere, good.");
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::VOLUME: {
|
2009-05-21 09:06:26 +00:00
|
|
|
SMesh *m = &(SK.GetGroup(SS.GW.activeGroup)->displayMesh);
|
2015-03-29 00:30:52 +00:00
|
|
|
|
2008-02-07 09:53:52 +00:00
|
|
|
double vol = 0;
|
|
|
|
int i;
|
|
|
|
for(i = 0; i < m->l.n; i++) {
|
|
|
|
STriangle tr = m->l.elem[i];
|
|
|
|
|
|
|
|
// Translate to place vertex A at (x, y, 0)
|
|
|
|
Vector trans = Vector::From(tr.a.x, tr.a.y, 0);
|
|
|
|
tr.a = (tr.a).Minus(trans);
|
|
|
|
tr.b = (tr.b).Minus(trans);
|
|
|
|
tr.c = (tr.c).Minus(trans);
|
|
|
|
|
|
|
|
// Rotate to place vertex B on the y-axis. Depending on
|
|
|
|
// whether the triangle is CW or CCW, C is either to the
|
|
|
|
// right or to the left of the y-axis. This handles the
|
|
|
|
// sign of our normal.
|
|
|
|
Vector u = Vector::From(-tr.b.y, tr.b.x, 0);
|
|
|
|
u = u.WithMagnitude(1);
|
|
|
|
Vector v = Vector::From(tr.b.x, tr.b.y, 0);
|
|
|
|
v = v.WithMagnitude(1);
|
|
|
|
Vector n = Vector::From(0, 0, 1);
|
|
|
|
|
|
|
|
tr.a = (tr.a).DotInToCsys(u, v, n);
|
|
|
|
tr.b = (tr.b).DotInToCsys(u, v, n);
|
|
|
|
tr.c = (tr.c).DotInToCsys(u, v, n);
|
|
|
|
|
|
|
|
n = tr.Normal().WithMagnitude(1);
|
|
|
|
|
|
|
|
// Triangles on edge don't contribute
|
|
|
|
if(fabs(n.z) < LENGTH_EPS) continue;
|
2015-03-29 00:30:52 +00:00
|
|
|
|
2008-02-07 09:53:52 +00:00
|
|
|
// The plane has equation p dot n = a dot n
|
|
|
|
double d = (tr.a).Dot(n);
|
|
|
|
// nx*x + ny*y + nz*z = d
|
|
|
|
// nz*z = d - nx*x - ny*y
|
|
|
|
double A = -n.x/n.z, B = -n.y/n.z, C = d/n.z;
|
|
|
|
|
|
|
|
double mac = tr.c.y/tr.c.x, mbc = (tr.c.y - tr.b.y)/tr.c.x;
|
|
|
|
double xc = tr.c.x, yb = tr.b.y;
|
2015-03-29 00:30:52 +00:00
|
|
|
|
2008-02-07 09:53:52 +00:00
|
|
|
// I asked Maple for
|
|
|
|
// int(int(A*x + B*y +C, y=mac*x..(mbc*x + yb)), x=0..xc);
|
2015-03-29 00:30:52 +00:00
|
|
|
double integral =
|
2008-02-07 09:53:52 +00:00
|
|
|
(1.0/3)*(
|
|
|
|
A*(mbc-mac)+
|
|
|
|
(1.0/2)*B*(mbc*mbc-mac*mac)
|
|
|
|
)*(xc*xc*xc)+
|
|
|
|
(1.0/2)*(A*yb+B*yb*mbc+C*(mbc-mac))*xc*xc+
|
|
|
|
C*yb*xc+
|
|
|
|
(1.0/2)*B*yb*yb*xc;
|
|
|
|
|
|
|
|
vol += integral;
|
|
|
|
}
|
2010-03-01 17:23:57 +00:00
|
|
|
|
2016-01-27 05:13:04 +00:00
|
|
|
std::string msg = ssprintf("The volume of the solid model is:\n\n"" %.3f %s^3",
|
2010-03-01 17:23:57 +00:00
|
|
|
vol / pow(SS.MmPerUnit(), 3),
|
|
|
|
SS.UnitName());
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
if(SS.viewUnits == Unit::MM) {
|
2016-01-27 05:13:04 +00:00
|
|
|
msg += ssprintf("\n %.2f mL", vol/(10*10*10));
|
2010-03-01 17:23:57 +00:00
|
|
|
}
|
2016-01-27 05:13:04 +00:00
|
|
|
msg += "\n\nCurved surfaces have been approximated as triangles.\n"
|
|
|
|
"This introduces error, typically of around 1%.";
|
|
|
|
Message("%s", msg.c_str());
|
2010-03-01 17:23:57 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::AREA: {
|
2010-03-01 17:23:57 +00:00
|
|
|
Group *g = SK.GetGroup(SS.GW.activeGroup);
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
if(g->polyError.how != PolyError::GOOD) {
|
2010-03-01 17:23:57 +00:00
|
|
|
Error("This group does not contain a correctly-formed "
|
|
|
|
"2d closed area. It is open, not coplanar, or self-"
|
|
|
|
"intersecting.");
|
|
|
|
break;
|
|
|
|
}
|
2015-03-27 15:31:23 +00:00
|
|
|
SEdgeList sel = {};
|
2010-03-01 17:23:57 +00:00
|
|
|
g->polyLoops.MakeEdgesInto(&sel);
|
2015-03-27 15:31:23 +00:00
|
|
|
SPolygon sp = {};
|
2016-05-25 12:08:19 +00:00
|
|
|
sel.AssemblePolygon(&sp, NULL, /*keepDir=*/true);
|
2010-03-01 17:23:57 +00:00
|
|
|
sp.normal = sp.ComputeNormal();
|
|
|
|
sp.FixContourDirections();
|
|
|
|
double area = sp.SignedArea();
|
|
|
|
double scale = SS.MmPerUnit();
|
|
|
|
Message("The area of the region sketched in this group is:\n\n"
|
|
|
|
" %.3f %s^2\n\n"
|
|
|
|
"Curves have been approximated as piecewise linear.\n"
|
|
|
|
"This introduces error, typically of around 1%%.",
|
|
|
|
area / (scale*scale),
|
|
|
|
SS.UnitName());
|
|
|
|
sel.Clear();
|
|
|
|
sp.Clear();
|
2008-07-20 11:27:22 +00:00
|
|
|
break;
|
2008-02-07 09:53:52 +00:00
|
|
|
}
|
2008-07-20 11:27:22 +00:00
|
|
|
|
2016-08-01 13:18:58 +00:00
|
|
|
case Command::PERIMETER: {
|
|
|
|
if(gs.n > 0 && gs.n == gs.entities) {
|
|
|
|
double perimeter = 0.0;
|
|
|
|
for(int i = 0; i < gs.entities; i++) {
|
|
|
|
Entity *e = SK.entity.FindById(gs.entity[i]);
|
|
|
|
SEdgeList *el = e->GetOrGenerateEdges();
|
|
|
|
for(const SEdge &e : el->l) {
|
|
|
|
perimeter += e.b.Minus(e.a).Magnitude();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
double scale = SS.MmPerUnit();
|
|
|
|
Message("The total length of the selected entities is:\n\n"
|
|
|
|
" %.3f %s\n\n"
|
|
|
|
"Curves have been approximated as piecewise linear.\n"
|
|
|
|
"This introduces error, typically of around 1%%.",
|
|
|
|
perimeter / scale,
|
|
|
|
SS.UnitName());
|
|
|
|
} else {
|
|
|
|
Error("Bad selection for perimeter; select line segments, arcs, and curves.");
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::SHOW_DOF:
|
2009-01-04 12:01:46 +00:00
|
|
|
// This works like a normal solve, except that it calculates
|
|
|
|
// which variables are free/bound at the same time.
|
2016-12-26 02:09:45 +00:00
|
|
|
SS.GenerateAll(SolveSpaceUI::Generate::ALL, /*andFindFree=*/true);
|
2009-01-04 12:01:46 +00:00
|
|
|
break;
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::TRACE_PT:
|
2008-07-20 11:27:22 +00:00
|
|
|
if(gs.points == 1 && gs.n == 1) {
|
|
|
|
SS.traced.point = gs.point[0];
|
|
|
|
SS.GW.ClearSelection();
|
|
|
|
} else {
|
|
|
|
Error("Bad selection for trace; select a single point.");
|
|
|
|
}
|
|
|
|
break;
|
2015-03-29 00:30:52 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::STOP_TRACING: {
|
2016-11-17 12:21:41 +00:00
|
|
|
std::string exportFile = SS.saveFile;
|
2016-05-04 03:12:06 +00:00
|
|
|
if(GetSaveFile(&exportFile, "", CsvFileFilter)) {
|
2015-12-27 08:09:00 +00:00
|
|
|
FILE *f = ssfopen(exportFile, "wb");
|
2008-07-20 11:27:22 +00:00
|
|
|
if(f) {
|
|
|
|
int i;
|
|
|
|
SContour *sc = &(SS.traced.path);
|
|
|
|
for(i = 0; i < sc->l.n; i++) {
|
|
|
|
Vector p = sc->l.elem[i].p;
|
|
|
|
double s = SS.exportScale;
|
2008-02-09 13:52:01 +00:00
|
|
|
fprintf(f, "%.10f, %.10f, %.10f\r\n",
|
2008-07-20 11:27:22 +00:00
|
|
|
p.x/s, p.y/s, p.z/s);
|
|
|
|
}
|
|
|
|
fclose(f);
|
|
|
|
} else {
|
2015-12-27 01:03:24 +00:00
|
|
|
Error("Couldn't write to '%s'", exportFile.c_str());
|
2008-07-20 11:27:22 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
// Clear the trace, and stop tracing
|
|
|
|
SS.traced.point = Entity::NO_ENTITY;
|
|
|
|
SS.traced.path.l.Clear();
|
|
|
|
InvalidateGraphics();
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2016-05-18 22:51:36 +00:00
|
|
|
default: ssassert(false, "Unexpected menu ID");
|
2008-07-20 11:27:22 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-11-14 15:16:50 +00:00
|
|
|
void SolveSpaceUI::ShowNakedEdges(bool reportOnlyWhenNotOkay) {
|
|
|
|
SS.nakedEdges.Clear();
|
|
|
|
|
|
|
|
Group *g = SK.GetGroup(SS.GW.activeGroup);
|
|
|
|
SMesh *m = &(g->displayMesh);
|
|
|
|
SKdNode *root = SKdNode::From(m);
|
|
|
|
bool inters, leaks;
|
|
|
|
root->MakeCertainEdgesInto(&(SS.nakedEdges),
|
|
|
|
EdgeKind::NAKED_OR_SELF_INTER, /*coplanarIsInter=*/true, &inters, &leaks);
|
|
|
|
|
|
|
|
if(reportOnlyWhenNotOkay && !inters && !leaks && SS.nakedEdges.l.n == 0) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
InvalidateGraphics();
|
|
|
|
|
|
|
|
const char *intersMsg = inters ?
|
|
|
|
"The mesh is self-intersecting (NOT okay, invalid)." :
|
|
|
|
"The mesh is not self-intersecting (okay, valid).";
|
|
|
|
const char *leaksMsg = leaks ?
|
|
|
|
"The mesh has naked edges (NOT okay, invalid)." :
|
|
|
|
"The mesh is watertight (okay, valid).";
|
|
|
|
|
|
|
|
std::string cntMsg = ssprintf("\n\nThe model contains %d triangles, from "
|
|
|
|
"%d surfaces.", g->displayMesh.l.n, g->runningShell.surface.n);
|
|
|
|
|
|
|
|
if(SS.nakedEdges.l.n == 0) {
|
|
|
|
Message("%s\n\n%s\n\nZero problematic edges, good.%s",
|
|
|
|
intersMsg, leaksMsg, cntMsg.c_str());
|
|
|
|
} else {
|
|
|
|
Error("%s\n\n%s\n\n%d problematic edges, bad.%s",
|
|
|
|
intersMsg, leaksMsg, SS.nakedEdges.l.n, cntMsg.c_str());
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
void SolveSpaceUI::MenuHelp(Command id) {
|
2017-01-05 10:39:08 +00:00
|
|
|
if((uint32_t)id >= (uint32_t)Command::LOCALE &&
|
|
|
|
(uint32_t)id < ((uint32_t)Command::LOCALE + Locales().size())) {
|
|
|
|
size_t offset = (uint32_t)id - (uint32_t)Command::LOCALE;
|
|
|
|
size_t i = 0;
|
|
|
|
for(auto locale : Locales()) {
|
|
|
|
if(i++ == offset) {
|
|
|
|
CnfFreezeString(locale.Culture(), "Locale");
|
|
|
|
SetLocale(locale.Culture());
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2008-02-09 13:52:01 +00:00
|
|
|
switch(id) {
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::WEBSITE:
|
2009-10-01 10:35:11 +00:00
|
|
|
OpenWebsite("http://solvespace.com/helpmenu");
|
2008-02-09 13:52:01 +00:00
|
|
|
break;
|
2015-03-29 00:30:52 +00:00
|
|
|
|
Convert all enumerations to use `enum class`.
Specifically, take the old code that looks like this:
class Foo {
enum { X = 1, Y = 2 };
int kind;
}
... foo.kind = Foo::X; ...
and convert it to this:
class Foo {
enum class Kind : uint32_t { X = 1, Y = 2 };
Kind kind;
}
... foo.kind = Foo::Kind::X;
(In some cases the enumeration would not be in the class namespace,
such as when it is generally useful.)
The benefits are as follows:
* The type of the field gives a clear indication of intent, both
to humans and tools (such as binding generators).
* The compiler is able to automatically warn when a switch is not
exhaustive; but this is currently suppressed by the
default: ssassert(false, ...)
idiom.
* Integers and plain enums are weakly type checked: they implicitly
convert into each other. This can hide bugs where type conversion
is performed but not intended. Enum classes are strongly type
checked.
* Plain enums pollute parent namespaces; enum classes do not.
Almost every defined enum we have already has a kind of ad-hoc
namespacing via `NAMESPACE_`, which is now explicit.
* Plain enums do not have a well-defined ABI size, which is
important for bindings. Enum classes can have it, if specified.
We specify the base type for all enums as uint32_t, which is
a safe choice and allows us to not change the numeric values
of any variants.
This commit introduces absolutely no functional change to the code,
just renaming and change of types. It handles almost all cases,
except GraphicsWindow::pending.operation, which needs minor
functional change.
2016-05-20 08:31:20 +00:00
|
|
|
case Command::ABOUT:
|
2013-09-22 10:50:59 +00:00
|
|
|
Message(
|
2013-10-28 05:28:42 +00:00
|
|
|
"This is SolveSpace version " PACKAGE_VERSION ".\n"
|
2013-09-22 10:50:59 +00:00
|
|
|
"\n"
|
|
|
|
"For more information, see http://solvespace.com/\n"
|
|
|
|
"\n"
|
|
|
|
"SolveSpace is free software: you are free to modify\n"
|
|
|
|
"and/or redistribute it under the terms of the GNU\n"
|
|
|
|
"General Public License (GPL) version 3 or later.\n"
|
|
|
|
"\n"
|
|
|
|
"There is NO WARRANTY, to the extent permitted by\n"
|
|
|
|
"law. For details, visit http://gnu.org/licenses/\n"
|
|
|
|
"\n"
|
2016-04-23 22:53:21 +00:00
|
|
|
"© 2008-2016 Jonathan Westhues and other authors.\n"
|
2013-09-22 10:50:59 +00:00
|
|
|
);
|
2008-02-09 13:52:01 +00:00
|
|
|
break;
|
|
|
|
|
2016-05-18 22:51:36 +00:00
|
|
|
default: ssassert(false, "Unexpected menu ID");
|
2008-02-09 13:52:01 +00:00
|
|
|
}
|
|
|
|
}
|
2013-09-19 04:33:12 +00:00
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
void SolveSpaceUI::Clear() {
|
2013-09-19 04:33:12 +00:00
|
|
|
sys.Clear();
|
|
|
|
for(int i = 0; i < MAX_UNDO; i++) {
|
|
|
|
if(i < undo.cnt) undo.d[i].Clear();
|
|
|
|
if(i < redo.cnt) redo.d[i].Clear();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-05-05 05:54:05 +00:00
|
|
|
void Sketch::Clear() {
|
2013-09-19 04:33:12 +00:00
|
|
|
group.Clear();
|
2016-02-17 10:03:07 +00:00
|
|
|
groupOrder.Clear();
|
2013-09-19 04:33:12 +00:00
|
|
|
constraint.Clear();
|
|
|
|
request.Clear();
|
|
|
|
style.Clear();
|
|
|
|
entity.Clear();
|
|
|
|
param.Clear();
|
|
|
|
}
|
2016-01-23 08:05:02 +00:00
|
|
|
|
|
|
|
BBox Sketch::CalculateEntityBBox(bool includingInvisible) {
|
2016-02-18 09:53:31 +00:00
|
|
|
BBox box = {};
|
2016-01-23 08:05:02 +00:00
|
|
|
bool first = true;
|
|
|
|
|
2016-10-30 10:26:31 +00:00
|
|
|
auto includePoint = [&](const Vector &point) {
|
2016-01-23 08:05:02 +00:00
|
|
|
if(first) {
|
|
|
|
box.minp = point;
|
|
|
|
box.maxp = point;
|
|
|
|
first = false;
|
|
|
|
} else {
|
2016-10-30 10:26:31 +00:00
|
|
|
box.Include(point);
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
for(const Entity &e : entity) {
|
|
|
|
if(e.construction) continue;
|
|
|
|
if(!(includingInvisible || e.IsVisible())) continue;
|
|
|
|
|
|
|
|
if(e.IsPoint()) {
|
|
|
|
includePoint(e.PointGetNum());
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch(e.type) {
|
|
|
|
// Circles and arcs are special cases. We calculate their bounds
|
|
|
|
// based on Bezier curve bounds. This is not exact for arcs,
|
|
|
|
// but the implementation is rather simple.
|
|
|
|
case Entity::Type::CIRCLE:
|
|
|
|
case Entity::Type::ARC_OF_CIRCLE: {
|
|
|
|
SBezierList sbl = {};
|
|
|
|
e.GenerateBezierCurves(&sbl);
|
|
|
|
|
|
|
|
for(const SBezier &sb : sbl.l) {
|
|
|
|
for(int j = 0; j <= sb.deg; j++) {
|
|
|
|
includePoint(sb.ctrl[j]);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
sbl.Clear();
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
default:
|
|
|
|
continue;
|
2016-01-23 08:05:02 +00:00
|
|
|
}
|
|
|
|
}
|
2016-10-30 10:26:31 +00:00
|
|
|
|
2016-01-23 08:05:02 +00:00
|
|
|
return box;
|
|
|
|
}
|
2016-04-02 13:34:17 +00:00
|
|
|
|
2016-04-10 11:25:26 +00:00
|
|
|
Group *Sketch::GetRunningMeshGroupFor(hGroup h) {
|
|
|
|
Group *g = GetGroup(h);
|
2016-04-02 13:34:17 +00:00
|
|
|
while(g != NULL) {
|
|
|
|
if(g->IsMeshGroup()) {
|
|
|
|
return g;
|
|
|
|
}
|
|
|
|
g = g->PreviousGroup();
|
|
|
|
}
|
|
|
|
return NULL;
|
|
|
|
}
|