@driven said:

http://www.sketchup.com/intl/en/download/gsu.html

I just pulled one down from here and I get
%(#0000FF)[SketchUp 8.0.16845, 2012 Trimble Navigation Limited]
maybe it's where your getting it from

john

I followed that link, downloaded the package (yet again) and inside it the Info.plist still says 8.0.15157. Are you downloading the free or pro? I wonder if just the free is broken?

Thanks
Steve

@slbaumgartner said:

@aerilius said:

Did you completely uninstall the previous version?
(When I messed around with different installs in different locations, I sometimes got a wrong version number, like if it was caused by remainders of another install.)

No, because it didn't tell me I needed to. I'll try that next.

[edit: Just now I completely uninstalled SU (so far as I know how - moved the application folder to trash and emptied), then downloaded a fresh image from the Trimble site, and it still says it is 8.0.15157. Is there somewhere else that it could be leaving cruft behind that I need to clean up? I hate it when there is no clear-cut uninstall!]

Thanks
Steve

I just used Pacifist to examine the disk image I downloaded from Trimble, and the info.plist in the package says 8.0.15157. This makes me think that the problem isn't on my end!

Steve

@aerilius said:

Did you completely uninstall the previous version?
(When I messed around with different installs in different locations, I sometimes got a wrong version number, like if it was caused by remainders of another install.)

No, because it didn't tell me I needed to. I'll try that next.

[edit: Just now I completely uninstalled SU (so far as I know how - moved the application folder to trash and emptied), then downloaded a fresh image from the Trimble site, and it still says it is 8.0.15157. Is there somewhere else that it could be leaving cruft behind that I need to clean up? I hate it when there is no clear-cut uninstall!]

Thanks
Steve

@aerilius said:

The latest installer for OS X should be 8.0.16845.
Is the one on this site correct? http://www.sketchup.com/gsu8/download.html

That's where I went, and after install it still says 8.0.15157. It seems to me that the install goes awfully quickly. Could something else going wrong? Is there anywhere that the installer would log errors?

Thanks
Steve

What is the current build version for SU 8.0 on Mac? If I check for updates via the "Check Web for Update" item on the SketchUp menu, it tells me there is a newer version available for update. But if I follow that link and install the "update" it is the exact same 8.0.15157 that I had before. Is the update process broken?

Thanks
Steve

[edit: somehow this got posted twice. sorry about that!]

@tba said:

After update --> SU crashed at startup on mac 10.8.2 !

Did someone know, which plugin(s) makes trouble at startup on mac mountain lion ?

Can someone called me, which plugins SU installed as default ?

Thanks

Updated and ran fine on mine. Must be some plugin you installed?

WARNING

Make sure to restore SketchUp to its distribution Ruby (1.8.5) before installing a version update to SketchUp! Otherwise the SU install will overwrite parts of your system-installed 1.8.7 Ruby and make it unusable (DAMHIKT)!

Steve

@dan rathbun said:

Just playin' devil's advocate:

Must the switch be done from within SketchUp, requiring a restart... or can desktop shortcuts (aka symbolic links, for you unix-like peeps,) be created to start SketchUp running whatever Ruby version is desired ?

(I had asked this question long ago, in a similar topic thread.)

Our switchover plugin is from within SketchUp and does require a restart (which it performs automatically for you). To select the version at launch time, you'd need to wrap it in a shell or Apple script that performs the shell commands I provided earlier. I don't think there is any way to tell SketchUp itself which Ruby to use as it launches...it behaves like it has a path to its distributed version coded into the executable.

Steve

@driven said:

hide then unhide the toolbar via right click [as the old apple button has been removed], I had an applescript that did it for me in the past...
should work

I may not have communicated clearly...the toolbar is visible and populated with a bunch of built-in tools that I placed there. Only the ones that I added from plugins are missing. Right-click doesn't affect this...

Update to the community: driven and I have got a plugin to do this Ruby swap nearly ready. Currently kicking it around to shake out any remaining bugs and packaging it for distribution. We'll put in the plugins forum soon.

Steve

Here's another one: I added some plugins' tools to the main toolbar using View->Customize Toolbar... Works great, but when SketchUp starts, these are missing from the toolbar on the blank window SU opens by default. If I open a window on an existing file or open another new window using the File menu, they reappear.

Seems to me this must be a sequencing problem: most likely SU creates the default window before it has loaded the plugins. Not a big deal, but a minor annoyance.

Steve

@driven said:

Still not wrapped, as I think I'll add it to my ON_OFF.rb and rework that to add a few new tricks this exercise has exposed.
However, this is now running in either of the two versions of SU I have installed at different Paths, and it should also add your native Ruby and Gem Paths on >1.8.5 [gems don't work on 1.8.5 unless you still have a full instal of both...]
[attachment=0:28ht225z]<!-- ia0 -->rubyVersion_change.rb<!-- ia0 -->[/attachment:28ht225z]
Should I delete all the other progression code? I did edit it to work, and it has a variety of other methods...

John,

Lots of problems with this code on my Mac. I'm pressed for time right now, will PM you later when I get a chance.

Steve

@driven said:

so, you need to double escape the system path, but single escape the ruby one.... aaahhhhhh

any testers, before I polish it?

Ah the joy of escapes! You need one \ to preserve the space in a path used by Ruby itself, but \ to pass along \ to preserve the space when the path will be sent to the system. Ack!!

I'll be tied up for a day or two with holiday obligations, but will be glad to try this out when I get some free time.

Steve

Dan,

I find those parts of the Ruby documentation ambiguous, as the phrase "obsolete constants" displays below VERSION when I view the page, as if, in the example you posted, it applies to RELEASE_DATE and PLATFORM but not to VERSION. In any case, it is clear that we should use RUBY_VERSION as there are examples on the table where using VERSION breaks

Steve.

@driven said:

Hi Steve,
I run as an admin, but not root, I need sudo for anything outside user space.
'Content' folders should have User read/write permissions, I thought.
I also run multiple copies of SU, the path for this one differs from norm and yours. [that may be the splat]

the other thing I have now added sleep 1 and a return before the cd / to reopen SU in both methods.

I may have done blanket permission change using Sketchup.app >> right click >> more info and change for all enclosed files, but I don't think so... but that should work to avoid 'sudo'.
alternatively do that to your 'User' folder after installing SU there?

just using the bits needed for a restart seems handy as well.

Hmm...there is a school of though that says ordinary users shouldn't be able to tamper within the subfolders of an app bundle, since they can destabilize the app in arbitrary ways. I once ran a utility that "fixes problems due to permissions", and I wonder if it reset the SU folders and files based on that thinking? Horse is out of the barn now, so without removing and reinstalling SU it's impossible for me to be sure. Maybe if another Mac user is watching this, they can look at their folders before either of our tweaks and tell us what permissions they see? The answer would be important so that your script could be shared successfully.

On a more basic level, after switching to 1.8.7, why would someone want to switch back? The only reason I have thought of is if you are writing plugins for the general Mac community, you might want to verify that they run on the as-installed SU with 1.8.5. So far, I haven't run into any old ones that won't run on 1.8.7. And if I do, provided they were distributed as open code, I'd be more inclined to fix them than to switch back to 1.8.5 just for their sake!

I had seen the problem Dan cites when I used the new Ruby console the Trimble guys posted on GitHub - VERSION on it returns 0.0.1; you have to use RUBY_VERSION to get the right string.

Steve

@driven said:

Hi Steve,
just got back and tested your method, works a treat, so I worked out a Ruby Console 'none sudo' version that works here, if it works for you I'll make it into a toggle button for switching from inside SU...

yes Dan I'll wrap it in a module...
john

Hi John,

On my Mac, the folders and files involved all have root ownership and rwxr-xr-x permissions, so without sudo I could change nothing. When I tried this script, SketchUp crashed (no bugsplat, just vanished!), and nothing changed. You aren't running as root are you? I can see how, after changing permissions, your script would be useful for toggling back and forth between versions, but I don't understand how it can work without either that tweak or sudo?

Steve

P.S. OK Dan, I deleted the code block

@driven said:

@unknownuser said:

(Wonder if John (driven) told me this - but I never got around to try it.)

Yes, Steve, you should have found it, maybe I used a different sting? ,but There is a ruby console version somewhere here.
I'm in 'The Isle of Man' for next 3 days so can't check...
Some jquery type dialogs need a gap created to get the options menu
Adding a margin often works, or try a textarea

Steve search my post to see some other mac tricks good and bad....
John

It was hiding away, but eventually I did find your prior post. Seems I am destined to follow ignorantly in your footsteps a year behind!

When analyzing the TestUp webdlg, I noticed a sort of catch-22: you can't open the WebKit inspector before loading the page, but that means you can't plant breakpoints in js that is executed as the page loads! The solution is to load the page, open the inspector, plant the breakpoints, and then use the right-click menu to reload the page. The breakpoints "stick" across the reload.

regards,
Steve

@wind-borne said:

If you delete line I highlighted near end of 3dshapestool.rb the toolbar will not load until you choose in Tool Palettes.

Ah! That indeed fixed it! I forgot that this tool was a plugin, not a built-in, and didn't think to edit the Ruby.

thanks,
Steve

I have this kind of problem too. Every time I start SketchUp I get a 3d Shapes Tool palette. I seldom use these tools, so the palette is just clutter to me, but I can't seem to keep it from reappearing. I tried all of the suggestions above, and SketchUp determinedly turns it back on. To me this smells like a programming feature (aka bug) in SketchUp on the Mac - somehow it is mishandling the palette states saved in the plist.

I don't know if this is common knowledge, but I didn't find a reference to it when searching sketchUcation, so I thought I'd share.

If you turn on the WebKitDeveloperExtras for SketchUp on a Mac, you can get the "Inspect element" pane/window to analyze and debug webdlg pages! Here's how:

Quit SketchUp

First, find out the bundle id for your installation of SketchUp:

• open a terminal window
• type mdls /Applications/Google\ SketchUp\ 8/SketchUp.app | grep BundleIdentifier
  You should get a line like:
  kMDItemCFBundleIdentifier = "com.google.sketchupfree8"
  (obviously, this is from a free version install - the bundle id string will be different on pro)

Next, enable the WebKitDeveloperExtras in SketchUp:

• type defaults write com.google.sketchupfree8 "WebKitDeveloperExtras" -bool TRUE
  (use the bundle id string you got above)

Now start SketchUp and open a tool that uses webdlg. If you right-click in the webdlg window, you will get a menu that says "Reload" and "Inspect Element". If you click the second choice, you will open the inspection pane/window (there is a setting on the inspector that chooses whether it opens as a pane in the target window or as a separate window). Now you can use the inspector to do things such as see which elements of the html and css affect what aspects of the display. You can also place breakpoints in javascript and single-step through the scripts to your heart's content. This technique eliminates the need to load your javascript up with alerts or similar debugging outputs, and can detect subtle errors that otherwise cause functions to abort silently.

Enjoy,
Steve