MK
Marius Kintel
Thu, Jun 23, 2016 1:10 PM
Hi Jamie,
Thanks for the digging!
On Jun 23, 2016, at 06:00 AM, Jamie_K vector76@gmail.com wrote:
- By fixing cgal 4.5 to be compatible with cmake 3.4.3
The latest MXE has CGAL 4.6.3 - perhaps that works better.
..but the better option is probably to upgrade MXE all the way to 4.8.1, to avoid having to maintain legacy code.
-Marius
Hi Jamie,
Thanks for the digging!
> On Jun 23, 2016, at 06:00 AM, Jamie_K <vector76@gmail.com> wrote:
>
> 2. By fixing cgal 4.5 to be compatible with cmake 3.4.3
>
The latest MXE has CGAL 4.6.3 - perhaps that works better.
..but the better option is probably to upgrade MXE all the way to 4.8.1, to avoid having to maintain legacy code.
-Marius
MD
Michele Denber
Thu, Jun 23, 2016 4:50 PM
The Close command from the File menu, is performing an Exit. I'd expect
it to close the current file but leave the program running. That is
AFAIK, the standard meaning of "close". Is this fixed in some newer
version?
Windows version 2014.12.25 (git 73163f2)
- Michele
The Close command from the File menu, is performing an Exit. I'd expect
it to close the current file but leave the program running. That is
AFAIK, the standard meaning of "close". Is this fixed in some newer
version?
Windows version 2014.12.25 (git 73163f2)
- Michele
TP
Torsten Paul
Thu, Jun 23, 2016 5:20 PM
Oh, that sounds like a bumpy road ahead with CGAL on MXE. If the
upgrade works, it would be very cool if that could be pushed to
the official MXE project.
I don't know if it became easier, but upgrading earlier versions
was quite tricky as they need to ship some kind of pre-generated
configuration file for the cmake process.
The MXE clone in the openscad project on github is only there
as staging area to prevent unexpected upgrades and help when we
need to add new packages.
ciao,
Torsten.
Oh, that sounds like a bumpy road ahead with CGAL on MXE. If the
upgrade works, it would be very cool if that could be pushed to
the official MXE project.
I don't know if it became easier, but upgrading earlier versions
was quite tricky as they need to ship some kind of pre-generated
configuration file for the cmake process.
The MXE clone in the openscad project on github is only there
as staging area to prevent unexpected upgrades and help when we
need to add new packages.
ciao,
Torsten.
MK
Marius Kintel
Thu, Jun 23, 2016 10:07 PM
Hi Michele,
We will close the program if you close the last open file.
-Marius
PS. Your version is pretty old. The latest official release is 2015.03-2.
Hi Michele,
We will close the program if you close the last open file.
-Marius
PS. Your version is pretty old. The latest official release is 2015.03-2.
> On Jun 23, 2016, at 12:50 PM, Michele Denber <denber@mindspring.com> wrote:
>
> The Close command from the File menu, is performing an Exit. I'd expect it to close the current file but leave the program running. That is AFAIK, the standard meaning of "close". Is this fixed in some newer version?
>
> Windows version 2014.12.25 (git 73163f2)
>
> - Michele
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
M
MichaelAtOz
Fri, Jun 24, 2016 1:51 AM
The Close command from the File menu, is performing an Exit. I'd expect
it to close the current file but leave the program running. That is
AFAIK, the standard meaning of "close". Is this fixed in some newer
version?
Windows version 2014.12.25 (git 73163f2)
- Michele
OpenSCAD mailing list
I'm not sure if it is in 2014.12.25 but current versions have an 'allow
opening multiple documents' advanced preference.
When set it operates the way you expect with multiple files, except closing
the final document closes the program. Which is logical, as the graphic
display window is undefined without a source file.
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
View this message in context: http://forum.openscad.org/Compiling-for-Windows-tp17766p17807.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
Michele wrote
> The Close command from the File menu, is performing an Exit. I'd expect
> it to close the current file but leave the program running. That is
> AFAIK, the standard meaning of "close". Is this fixed in some newer
> version?
>
> Windows version 2014.12.25 (git 73163f2)
>
> - Michele
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@.openscad
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
I'm not sure if it is in 2014.12.25 but current versions have an 'allow
opening multiple documents' advanced preference.
When set it operates the way you expect with multiple files, except closing
the final document closes the program. Which is logical, as the graphic
display window is undefined without a source file.
-----
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
--
View this message in context: http://forum.openscad.org/Compiling-for-Windows-tp17766p17807.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
MD
Michele Denber
Sat, Jun 25, 2016 5:36 PM
On 06-23-2016 9:51 PM, MichaelAtOz wrote:
I'm not sure if it is in 2014.12.25 but current versions have an 'allow
opening multiple documents' advanced preference.
When set it operates the way you expect with multiple files, except closing
the final document closes the program. Which is logical, as the graphic
display window is undefined without a source file.
Yes, but that does not require exiting the program. When you first
start the program, the graphics window is blank until you start writing
code and rendering. This is the way Microsoft Word, CorelDraw, and
Photoshop all work. If you have one file open and click Close, the file
is closed but the program remains running with a blank text or graphics
window.
That's the way every program I've ever used that offers a Close command
works. Closing the last file leaves the program running with a blank
window ready to either open a new file or start creating a new
document. I submit that Openscad is non-standard in that regard.
- Michele
On 06-23-2016 9:51 PM, MichaelAtOz wrote:
>
> I'm not sure if it is in 2014.12.25 but current versions have an 'allow
> opening multiple documents' advanced preference.
> When set it operates the way you expect with multiple files, except closing
> the final document closes the program. Which is logical, as the graphic
> display window is undefined without a source file.
>
Yes, but that does not require exiting the program. When you first
start the program, the graphics window is blank until you start writing
code and rendering. This is the way Microsoft Word, CorelDraw, and
Photoshop all work. If you have one file open and click Close, the file
is closed but the program remains running with a blank text or graphics
window.
That's the way every program I've ever used that offers a Close command
works. Closing the last file leaves the program running with a blank
window ready to either open a new file or start creating a new
document. I submit that Openscad is non-standard in that regard.
- Michele
KS
Kenneth Sloan
Sat, Jun 25, 2016 7:39 PM
Heh…
I nominate “Openscad is non-s
Kenneth Sloan
KennethRSloan@gmail.com
Vision is the art of seeing what is invisible to others.
On Jun 25, 2016, at 10:36 , Michele Denber denber@mindspring.com wrote:
On 06-23-2016 9:51 PM, MichaelAtOz wrote:
I'm not sure if it is in 2014.12.25 but current versions have an 'allow
opening multiple documents' advanced preference.
When set it operates the way you expect with multiple files, except closing
the final document closes the program. Which is logical, as the graphic
display window is undefined without a source file.
Yes, but that does not require exiting the program. When you first start the program, the graphics window is blank until you start writing code and rendering. This is the way Microsoft Word, CorelDraw, and Photoshop all work. If you have one file open and click Close, the file is closed but the program remains running with a blank text or graphics window.
That's the way every program I've ever used that offers a Close command works. Closing the last file leaves the program running with a blank window ready to either open a new file or start creating a new document. I submit that Openscad is non-standard in that regard.
- Michele
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Heh…
I nominate “Openscad is non-s
--
Kenneth Sloan
KennethRSloan@gmail.com
Vision is the art of seeing what is invisible to others.
> On Jun 25, 2016, at 10:36 , Michele Denber <denber@mindspring.com> wrote:
>
> On 06-23-2016 9:51 PM, MichaelAtOz wrote:
>>
>> I'm not sure if it is in 2014.12.25 but current versions have an 'allow
>> opening multiple documents' advanced preference.
>> When set it operates the way you expect with multiple files, except closing
>> the final document closes the program. Which is logical, as the graphic
>> display window is undefined without a source file.
>>
> Yes, but that does not require exiting the program. When you first start the program, the graphics window is blank until you start writing code and rendering. This is the way Microsoft Word, CorelDraw, and Photoshop all work. If you have one file open and click Close, the file is closed but the program remains running with a blank text or graphics window.
>
> That's the way every program I've ever used that offers a Close command works. Closing the last file leaves the program running with a blank window ready to either open a new file or start creating a new document. I submit that Openscad is non-standard in that regard.
>
> - Michele
>
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
KS
Kenneth Sloan
Sat, Jun 25, 2016 7:44 PM
Heh…
I nominate “Openscad is non-standard” as the understatement of the year.
In a language where a cube may have different H,W,D, and where coders specify hex-nuts as “cylinder”s, I don’t think the slightly different handling of “Close” makes it on to the first page of examples of “non-standard” usage.
You were surprised. Get over it. I wouldn’t be surprised if there were not 10 existing OpenSCAD users who would complain about things “breaking” if the behavior were changed.
and, besides - working differently from Microsoft Word, CorelDraw, and Photoshop is not prima facie evidence of being “wrong”.
Being “different” is not always a bad thing.
--
Kenneth Sloan
KennethRSloan@gmail.com
Vision is the art of seeing what is invisible to others.
On Jun 25, 2016, at 10:36 , Michele Denber denber@mindspring.com wrote:
On 06-23-2016 9:51 PM, MichaelAtOz wrote:
I'm not sure if it is in 2014.12.25 but current versions have an 'allow
opening multiple documents' advanced preference.
When set it operates the way you expect with multiple files, except closing
the final document closes the program. Which is logical, as the graphic
display window is undefined without a source file.
Yes, but that does not require exiting the program. When you first start the program, the graphics window is blank until you start writing code and rendering. This is the way Microsoft Word, CorelDraw, and Photoshop all work. If you have one file open and click Close, the file is closed but the program remains running with a blank text or graphics window.
That's the way every program I've ever used that offers a Close command works. Closing the last file leaves the program running with a blank window ready to either open a new file or start creating a new document. I submit that Openscad is non-standard in that regard.
- Michele
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Heh…
I nominate “Openscad is non-standard” as the understatement of the year.
In a language where a cube may have different H,W,D, and where coders specify hex-nuts as “cylinder”s, I don’t think the slightly different handling of “Close” makes it on to the first page of examples of “non-standard” usage.
You were surprised. Get over it. I wouldn’t be surprised if there were not 10 existing OpenSCAD users who would complain about things “breaking” if the behavior were changed.
and, besides - working differently from Microsoft Word, CorelDraw, and Photoshop is not prima facie evidence of being “wrong”.
Being “different” is not always a bad thing.
--
Kenneth Sloan
KennethRSloan@gmail.com
Vision is the art of seeing what is invisible to others.
> On Jun 25, 2016, at 10:36 , Michele Denber <denber@mindspring.com> wrote:
>
> On 06-23-2016 9:51 PM, MichaelAtOz wrote:
>>
>> I'm not sure if it is in 2014.12.25 but current versions have an 'allow
>> opening multiple documents' advanced preference.
>> When set it operates the way you expect with multiple files, except closing
>> the final document closes the program. Which is logical, as the graphic
>> display window is undefined without a source file.
>>
> Yes, but that does not require exiting the program. When you first start the program, the graphics window is blank until you start writing code and rendering. This is the way Microsoft Word, CorelDraw, and Photoshop all work. If you have one file open and click Close, the file is closed but the program remains running with a blank text or graphics window.
>
> That's the way every program I've ever used that offers a Close command works. Closing the last file leaves the program running with a blank window ready to either open a new file or start creating a new document. I submit that Openscad is non-standard in that regard.
>
> - Michele
>
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
MD
Michele Denber
Sat, Jun 25, 2016 8:37 PM
On 06-25-2016 3:44 PM, Kenneth Sloan wrote:
Heh…
I nominate “Openscad is non-standard” as the understatement of the year.
In a language where a cube may have different H,W,D, and where coders specify hex-nuts as “cylinder”s, I don’t think the slightly different handling of “Close” makes it on to the first page of examples of “non-standard” usage.
You were surprised. Get over it.
This is what I get for trying to help? Get over it?? Well then yes yes
Ken, you've totally convinced me. "Close" should mean "Exit" after
all. Also "Export" should mean "set the basic unit size to the parsec"
and "New" should mean "cd / ; rm -rf". That's different too.
And "Save" should mean "Welcome to my block list". Like this.
- Michele
On 06-25-2016 3:44 PM, Kenneth Sloan wrote:
> Heh…
>
> I nominate “Openscad is non-standard” as the understatement of the year.
>
> In a language where a cube may have different H,W,D, and where coders specify hex-nuts as “cylinder”s, I don’t think the slightly different handling of “Close” makes it on to the first page of examples of “non-standard” usage.
>
> You were surprised. Get over it.
>
This is what I get for trying to help? Get over it?? Well then yes yes
Ken, you've totally convinced me. "Close" should mean "Exit" after
all. Also "Export" should mean "set the basic unit size to the parsec"
and "New" should mean "cd / ; rm -rf". That's different too.
And "Save" should mean "Welcome to my block list". Like this.
- Michele