Open GoogleCodeExporter opened 9 years ago
Hi Mike,
Sorry for the trouble. The Mac versions works no differently than the PC
version(except as noted with the layout window not displaying).
The message would indicate that some of your parts are huge - I would guess
that there is something in your model which isn't quite right. Often this is
something like a set of parts which have been grouped together into a single
component more than once. What I mean is that Cutlist ignores the top most
component if there are components nested in it but sometimes there ends up
being two top level components, if you know what I mean. Cutlist then ignores
the first but uses the second and if the second is a an amalgamation of the
nested parts underneath it, it thinks it is a component which should be layed
out - and these top level components look like a very large solid. The 'solid'
is the blue box which appears in your model when you double click on it. That's
what cutlist uses to determine the size of the component.
If it detects something very large ( for example your entire piece is a solid),
then there is no way to slice this part up to make it fit on all of the layout
pieces.
Check your cutlist - are the dimensions what you expect?
Hope this triggers something and you are able to make some progress.
Steve
Original comment by daltx...@gmail.com
on 20 Nov 2012 at 2:17
Original comment by daltx...@gmail.com
on 20 Nov 2012 at 2:21
Hello,
I'm having the same problem as described by Mike. I am using Sketchup 7 with
cutlist 4.5.1. I looked at the sizes of the sheet, but they are not extremely
large. I would appreciate some help.
Thanks,
Daniel
Original comment by danielop...@gmail.com
on 4 Dec 2012 at 4:17
I am also having trouble with the cutlist layout on my MAC. Using Sketchup 8.0
and Cutlist 4.1.4. SVG is not the work around to display the cut layout--at
least it doesn't work for me. Any thoughts are appreciated.
Thanks,
DW
Original comment by DAWebe...@gmail.com
on 9 Dec 2012 at 8:00
Ok, this is most peculiar. I've changed nothing for Macs and they seem to be
starting to have trouble now. I need more info though.
Can someone send me a copy of their model or put it somewhere I can download it
and I can see if I can eliminate something to do with the model.
Also, if someone could enable the ruby window in Sketchup - then try it again -
then post the output of the ruby window - there might be something in there
which would give me a hint.
Thanks,
Steve
Original comment by daltx...@gmail.com
on 9 Dec 2012 at 9:14
I've been experiencing similar quirks when I run Sketchup on my Macs. On my
Mac at home which is running Lion, once I run Cutlist and try to print anything
my screen gets locked into a strange state where I can't zoom in and out and my
image gets all stretched out of proportion. I have to exit the program to get
out of this wiered locked proportion state. The Mac at work doesn't have this
problem. Another glitch that I have noticed is that on the Mac at work (Snow
Leopard, the Cutlist dialog boxes which you can enter key words for parts and
sheet goods are black (rather than white)so you can't see what you are typing.
the Mac running Lion doesn't have this problem. I've experienced no issues at
all running Sketchup on PC's running Windows 7. Thanks so much for the effort
you've put into this valuable program for woodworkers! Despite the glitches i
have experienced with Macs, it's still a great little plugin.
Thank you!
Eric.
Original comment by ericmcr...@gmail.com
on 28 Dec 2012 at 4:16
v4.1.5 actually addressed the black box issue for Macs - though I have since
found out that this was indeed a Safari issue on a particular version released
by Apple. In 4.1.5 I've changed the background color to a dark blue with white
text, so either way, it should show up ok.
It does now seem to me that all of the glitches with Macs have to do with
Safari (Whether you use Safari as your default browser or not, Sketchup uses
Safari as its default browser on Macs) as different people are experiencing
different issues with different versions.
I don't really have a solution yet - the plugin was designed to rely as little
as possible on the browser or rather to use the most common features of all
browsers, specifically so that there is no need to customize for any particular
platform. Constant tinkering by browser developers means that this can change
at any time.
On the other hand, I will continue to look for ways to reduce reliance on the
browser capabilities.
Steve
Original comment by daltx...@gmail.com
on 29 Dec 2012 at 6:00
Original issue reported on code.google.com by
mikemccl...@mac.com
on 19 Nov 2012 at 3:16