This also works around the bug in GTK in its file system tracking/file
open dialog that causes a crash when a file (in a directory it is tracking,
such as the previous directry where an STL was sliced from) is modified
with vim.
Steps to reproduce the bug:
1) Slice a file from the GUI
2) vim test.stl in the same directory
3) i hello ESC ZZ
4) if Slic3r didn't crash to a gtk assertion failure, jump to step 2
5) if still no luck, your gtk isn't broken. What version do you have?-)
fix typo that put things in the wrong position
use int() builtin instead of POSIX::floor()
fix typo
use alternate method of creating local routines
remove aliases for new duplicate option
use coderefs for linear interpolate function, make binary insertion sort inline
add \n at end of die message regarding too many objects for print area
fix case where no duplication is done
fix whitespace according to slic3r coding style
assume 200x200 bed area if center is 0,0
Some cleanup to the autoarrange duplication logic
* Added link to website for updates
* Moved 'Slice…' button to the right as this more logically follows the
user's flow through the application
* Moved version information to the middle right under the App name (on
OS X anyway) as it is clearer what the version is referring to
* Added spacing between the buttons
* Removed colon after 'version' as this is the UI convention in about
boxes
* Changed 'Load' to 'Open' as this is the more commonly used term
* Truncated 'Configuration' to 'Config' to save space, and I believe it
is still clear what it means
* Added open and save config to File menu as this is more conventional
location
* Simplified some wording
* Rephrased the tabs to be more succinct, I believe they still make
sense
* Fixed a spelling
* Replaced '…' with proper ellipses character
