@ntxdave said: If I am brave enough, I will post some of this stuff when I am done (give you a good chuckle for the day). OK, here is what I wound up with. [image: 42hG_ntxdave_Coupler.PNG]

Deleting stuff doesn't actually remove everything from the file. Go to Window/Model Info/Statistics and click Purge Unused... For starters.

As Dave says, many of the EW & PluginStores versions are now compatible with v2014 - some just 'were' already! If you have 'other' plugins from elsewhere - and there are no obvious updates available - then you can try moving copies over... but do them individually, and restart after each one is added, to see if that new addition breaks v2014. If it produces errors, then disable that plugin and contact the author about an update

@blenkey said: click ctrl, polygon will toggle between corner and centre of line. This feature was added after this thread, so the ctrl toggle of polygons doesn't work in versions before 2015.

Thanks ever so much for the response(s) - I will give it a try!

thanks for the reply.

Thanks guys, I figured it was just something to report just in case no one else had already, unlikely thought that might have been!

@jql said: Quad face tools: 1 - Select loops and rings 2 - Soften selected loops and rings 3 - Deactivate View > Hidden geometry 4 - Box select everything visible (diagonal lines and faces) 5 - Use selection toys to remove faces Thank you so much for your help! That is smart!

g_wilson, I attempted to follow your directions, but failed due to noobness. I got a bit lost there, especially in the "select instances" step (could not find that in any menu/pop-up menu?). I did mess around with components, but getting Sketchup 2014 to transfer changes from one component member to all of them . . . didn't work. Selecting them all and scaling them all simultaneously brought about the usual behavior (centers of circles moving around). So, I solved my problem by starting from scratch and using circles of the needed size instead of scaling anything I had derived from another model.

@jim said: If you click the Fly-out menu, and select "Remove Collection from Favorites", are you able to remove it? hi jim, no, that is the point. remove collection gives you the selection of collection, which are at the bottom of the pulldown menue. this one is on the top..... stan [image: 9gVH_Clipboard02.jpg] [image: i0RG_Clipboard03.jpg]

oh merci !! le plugin d'Albert m'a l'air fantastique ! je vais le voir tous de suite ! , et pour le reste j'avais deja essayé comme pour la courbe sur la sphere puis TUBEALONGPATH mais sa a pas l'effet voulu que je voulais on vas dire

I can't log into the Warehouse anymore with my main browser (Cyberfox, a 64bit Firefox variant), however, with Chrome it works. I just get a screen with three rotating circles and different symbols, and then the ruby symbol stops rotating and I get redirected to the warehouse without being signed in. With Chrome, the ruby symbol and the right sketchup symbol stop spinning, then I get signed in. Does anyone have an idea what could cause this? Most likely it has nothing to do with add-ons, since I can't sign in in safe mode as well. edit: Solved the problem by deleting cookies.

Thank you for the profile advice. I will immediately do that. As for the OpenGL settings - I will experiment in that area. Thanks again.

Ok thx Gilles, can you learn me how to made that ? Je n'ai pas acces au compte francais

@Tomot You are over thinking this. You will need some spaces in any language's code, so that the 'parts' can be differentiated by the interpreter. The only errant spaces you have flagged up so far are the ones I had previously warned against, and had been advised against in the earlier versions of Ruby too - because although they were 'tolerated' they could be deprecated and become unacceptable... and now they have been! To reiterate... A ' method' can sometimes take an argument or arguments [ .upto(666), .add_line(pt1, pt2), etc] - these arguments are always best passed inside parenthesizes ()... The opening ( should come immediately after the last character of the method, with no space between them. So all you need to do is search for ' (' and then decide it you make it into a simple ' (' when it occurs immediately after a method. Some spaces in code are 'optional' and using them simply helps 'readability' when editing - just like consistent indenting of code-blocks will - but again that was ever so: e.g. xx=12.3 v. xx = 12.3 From what I've seen of your screen-grab images, you have sometimes included other () in parts of your code - sometimes they are not necessary at all. if xxx && yyy is fine. if (xxx && yyy) is too, but the () are NOT needed at all, unless you are nesting tests like this: if xxx && (yyy || zzz) when you need them... All v2014 Ruby2.0 has done is to stop accepting some syntax that was already advised against in earlier versions too. It has not 'moved the goalposts' - rather it has 'set them in firmer foundations'... The advantages of v2.0 far outweigh the inconvenience of tidying up old poorly drafted code. The few other minor changes in its methods, like 'array_to_string', actually bring it to be more aligned with other similar languages like Perl... These changes are unlikely to affect the vast majority of scripts anyway, and if they do they do then it is easily spotted and resolved anyway... Be assured that if you scripts are updated and they work properly for you in v2014, then they should work for anyone else using the same version [and OS and Pro/Make***]. ***If in the unlikely event that one of your scripts contain some OS specific or Pro [v.Make] methods/code then of course, without testing your script on the alternative OS/Pro compatibility cannot be ensured - but that was ever thus...

Tell me about it... Look what's just cropped up with users of v2014 who include a' in their Windows User name... their Plugins won't load... OR v2014 Windows Users who manage to setup an accented-name that is not UTF8 encoded [unexpectedly surprisingly easy!], bringing us all back to the pre-v2014 days of accented-user-names dismally failing when accessing FILE/TEMP etc... it can be fixed in v2014 by considerable [unexpected] convoluted hoop-jumping by plugins-authors, who now need to avoid an issue that Ruby2.0 was mean to circumvent - AND NOT MAKE WORSE [FFS]!

@jclements said: Is this being supported at all? Nope. Not supported for years.