@beginner said:

It would be nice if LO could handle Ruby plugins
LO could be powerful as SU

Now that would be an AWESOME idea! And also have a plugin interface for external renderers.

@john2 said:

2. Thumbnail support in folder containing SketchUp files for 64 bit windows 7 operating system

+1!!!![/quote]

It WAS really nice having thumbnails in 64-bit Windows.....

Disappearing text was a bug in SketchUp that I thought was fixed.
The problem is when the text or the leaders span tile rendering
boundaries. Open the PDF in Adobe's viewer. Click on the rendered
image and you'll see how the view is rendered into tiles. See
if the missing text is on the tile boundaries. If so its the bug.

How 'bout them working menu items!?!?

@toddwilli said:

I have searched the forums for info on this problem, but found nothing since 2009!
Anyone got any good ideas? If this was a known problem back in ver 6, why has it not been solved by ver 8? Thanks for any help.

Its was/is a known problem, so much so, that an entire application was created to solve this problem, it's called LayOut.

Its defined in our C++ code. I took a look at what's going on.
It does-

<span class="syntaxdefault">  static VALUE g_SketchUp_Version </span><span class="syntaxkeyword">=</span><span class="syntaxdefault"> GetRubyInterface</span><span class="syntaxkeyword">(</span><span class="syntaxdefault">ver</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">GetVersion</span><span class="syntaxkeyword">());<br /></span><span class="syntaxdefault">  rb_define_readonly_variable</span><span class="syntaxkeyword">(</span><span class="syntaxstring">"$sketchup_version"</span><span class="syntaxkeyword">,</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">&</span><span class="syntaxdefault">g_SketchUp_Version</span><span class="syntaxkeyword">);</span><span class="syntaxdefault"> </span>

Just to show some history of SU code-

<span class="syntaxdefault">int CVersionInfo</span><span class="syntaxkeyword">;;</span><span class="syntaxdefault">GetVersion</span><span class="syntaxkeyword">()</span><span class="syntaxdefault"> const </span><span class="syntaxkeyword">{<br /></span><span class="syntaxdefault">  return CVersionInfo</span><span class="syntaxkeyword">;;</span><span class="syntaxdefault">GetVersion</span><span class="syntaxkeyword">(</span><span class="syntaxdefault">m_major</span><span class="syntaxkeyword">,</span><span class="syntaxdefault"> m_minor</span><span class="syntaxkeyword">,</span><span class="syntaxdefault"> m_buildNumber</span><span class="syntaxkeyword">);<br />}<br /><br /></span><span class="syntaxdefault">int CVersionInfo</span><span class="syntaxkeyword">;;</span><span class="syntaxdefault">GetVersion</span><span class="syntaxkeyword">(</span><span class="syntaxdefault">int major</span><span class="syntaxkeyword">,</span><span class="syntaxdefault"> int minor</span><span class="syntaxkeyword">,</span><span class="syntaxdefault"> int build</span><span class="syntaxkeyword">)</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">{<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// This is a MAJOR KLUDGE necessary because we never anticipated over 1000<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// builds for a single SketchUp release.  SketchUp depends on a version number<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// of the form 1000000 * Major release number + 1000 * Minor release number +<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// build number.  Thus if the build number exceeds 999, it rolls over to the<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// minor build number - which is wrong.  On the RASH assumption that no one<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// REALLY cares about the build number anymore and that the minor release<br /></span><span class="syntaxdefault">  </span><span class="syntaxcomment">// number will never exceed 999, I made the following modification;<br /></span><span class="syntaxdefault">  if </span><span class="syntaxkeyword">(</span><span class="syntaxdefault">minor </span><span class="syntaxkeyword">></span><span class="syntaxdefault"> 999</span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault">    minor </span><span class="syntaxkeyword">=</span><span class="syntaxdefault"> 999</span><span class="syntaxkeyword">;<br /></span><span class="syntaxdefault">  if </span><span class="syntaxkeyword">(</span><span class="syntaxdefault">build </span><span class="syntaxkeyword">></span><span class="syntaxdefault"> 999</span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault">    build </span><span class="syntaxkeyword">=</span><span class="syntaxdefault"> 999</span><span class="syntaxkeyword">;<br /></span><span class="syntaxdefault">  return </span><span class="syntaxkeyword">((</span><span class="syntaxdefault">major </span><span class="syntaxkeyword">*</span><span class="syntaxdefault"> 1000000</span><span class="syntaxkeyword">)</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">+</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">(</span><span class="syntaxdefault">minor </span><span class="syntaxkeyword">*</span><span class="syntaxdefault"> 1000</span><span class="syntaxkeyword">)</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">+</span><span class="syntaxdefault"> build</span><span class="syntaxkeyword">);<br />}</span><span class="syntaxdefault"> </span>

@teamsda said:

• The black lines I am seeing are around the texture image where there are not items behind it. See Example_2.png
  Christian

I've seen this before, but it was white edges around images.
If you're using Adobe's pdf viewer, open Edit->Preferences...
Select "Page Display"
In the Rendering section there's "Smooth images".
Make sure that's not selected. You might have to turn off "Use 2D graphics acceleration".
Or if "Use 2D graphics acceleration" isn't selected, try turning it on.

@teamsda said:

• The X lines going vertical and horizontal through my export can bee seen in example 1 or 2. Example 2 has nothing but a single face it still has the lines.
  Christian

Those lines are actually the boundaries between the rendered tiles.
We need to tile to prevent the old "Red X" problem once seen in v1,
which was caused from running out of memory. If you open the
pdf in a viewer that can select items, you'll see the tiles when
you select them.

There's a Ruby command to export a transparent background-

keys = {
:filename => "c:/tmp/write_image.png",
:width => 640,
:height => 480,
:antialias => false,
:compression => 0.9,
:transparent => true
}
model = Sketchup.active_model
view = model.active_view
view.write_image keys

Looking at the add_group Ruby code, its the same on both platforms.
One reason (don't know if this is true) it could be slower on the Mac
is the notifications that are sent around could be updating the Mac
UI, like the component browser. This may be more efficiently done on
the PC.

Also, the same code (duplicate code/cut-n-pasted it looks like) that
I fixed in the C++ API was also being used in the Ruby code.
The bug report only mentioned the C++ API, so that's what got fixed.

The menu problems are caused by-
http://forums.sketchucation.com/viewtopic.php?f=15&t=27941&hilit=+menu#p243583

I'll take a look today and see if I can fix the root problem rather than have a witch hunt for the plugins causing this problem.
I know what's causing it and hopefully it won't be too intrusive to fix.

LayOut documents won't render the text the same moving a document from one OS to another.

If you can post an example LO file or send me the file, we (LO developers) can take a look.

Insert the first model where you want it on the page.
Then put something like a + (2 lines crossing each other and grouped (doesn't matter what you draw)) on a shared layer so that you can see the + on every page.
Move the + using precise move to some point on your model.
Then add a new page and insert your next model.
Using precise move, move the model to line up with the +.

Can you list the specifics of the font (font family name) that are not working correctly?
The font is needed to debug the problem.

@chip said:

I have not done anything special, just using Layout blank sheets and I am getting this error all the time. More then 75% of the files I start end up giving me this error. Does anyone know the answer. I love this program, but I can't keep copying everything over to new files to save. Please HELP!!!! Could this have anything to do with an imported image's resolution?

I assume you're running SU 8/LO 3. Your status shows SU 7. In LO 3 there was a bunch of work done to prevent corrupted documents from saving. If it was allowed to save, then the saved file would be corrupt. Most corrupt files had connections (leaders/dimensions). If you could provide more details, like a LO file that you start with and the steps that you did to not be able to save, that would be helpful in fixing the bug.

Your status shows you're using SU 7. There was a bunch of work on HLR in Su 8. Can you try SU 8 to see if there's a difference?

Check out-
http://sketchup.google.com/intl/en/spectrum.html
Search for Project Spectrum.

Invalidate sends a message (WM_PAINT) requesting the view needs refreshed.
view.refresh actually calls the view draw method.

Short answer, I would not recommend using a Scene in LO that doesn't snapshot all the Scene's properties.

Long answer...
If you don't snapshot all the properties for a SU Scene in LO, you're not guaranteed to always get the same rendering each time you update in SU and then update the model in LO. What LO basically does for each model rendering is open the SKP and switch to the Scene you want rendered. If you change a setting that's not being captured in a Scene and you change that same setting between saves in SU and updates in LO, you'll see what I mean.