[Plugin] SketchUcation Tools 2.6
-
Did you install SketchUp v2014 on the main system-drive [C: ] or is it on another drive-letter ?
Do you always get this error as SketchUp starts, or is it when you try to open a SKP by double-clicking its icon, AND that SKP is not on the same drive as SketchUp.exe itself ?
Or to put it another way... if you open SketchUp with a new empty SKP by double-clicking your Desktop shortcut to SketchUp.exe what happens ? Similar/Different/No errors ??There is known bug in v2014 M0 where this configuration of file locations and usage can stop its Ruby2.0 loading properly, and then you can get errors as a partial Ruby can't parse some strings or find vital ruby methods...
Please post the results of the following in the Ruby Console for v2014...
` Sketchup.find_support_file('Plugins')
Sketchup.find_support_file('Tools')
Sketchup.find_support_file('SketchUp.exe')
$:
$".grep(/gems/)`
And also a file-path for one of the SKPs that is showing this issue...
I don't think it's directly related to our toolset per se, but rather your configuration...
But we need to get to the bottom of this...
-
@kienhp said:
Not run in skechUp 2014, why?
Because Vietnamese encoding is not supported by Ruby yet.
Bug # 7742 : System encoding (Windows-1258) is not recognized by Ruby to convert back to UTF-8
One user changed his Regional and Langauge settings to US English to overcome this:
StackOverflow : Error installing Rubygems on ruby command prompt in Win7
-
I was wondering about the update system; it's not working as I would expect.
I have some plugins by Fredo installed; these come with its own update checker. However, I don't really like the way it pops up every so many days. It's a bit intrusive - especially if I have to teach. Pupils are easily spooked by an extra toolbar or window.
All that aside, however, I still leave it on, since it regularly shows updates that do not show in the SketchUcation Plugin store. I can see that my installed Fredo-plugins have different version numbers from the ones in the list, but still there is no update button, and it doesn't show up in the updates list.
So eventually I clicked on through until a button 'install extension' became visible. This is a bit counter-intuitive though. -
Did you install them from the PluginStore initially?
We can only track your activity in the PluginStore since it's launch. Anything you do outside that environment is outta our control.
We could add the ability to track your every movement. #youarebeingwatched
-
Hi, pyroluna:
I don't know if this works, or if you really want to do this, but Fredo's Check for updates has an interval box ordinarily set at 15 days.
Window>Libfredo Settings>Check plugins for update: the interface appears, and at the bottom of the frame is the input box for the interval. Maybe set to zero, or 99?
I could not find in the information manual anything, nor any setting in Program file subfolders Plugins, but I have seen registry titles relating to this during routine security scans on my system.
I do not advocate messing in the registry, just to say. -
@pyroluna said:
I was wondering about the update system; it's not working as I would expect.
The update system in 2.5.1 compares your user's latest downloaded plugin version to the curent available version in the store. If there is any difference the plugin will show up in the update list.
So:
- The plugin won't show up in the update list if you haven't downloaded the prevous version from the PluginStore.
- The plugin won't show up in the update list if you have updated it on an other device. (As in this case the latest download by you is up-to date)
We will refine this in the next (2.6) version by adding your device ID to the comparasion.
-
Updated to 2.6.0
4x times faster downloads
New Bundles features in My SetUp
Tons of tweaks and bugfixes
Anyone on 2.5 has until the end of the week to upgrade before we shut it down.
-
Love the new bundle feature!
-
I have downloaded for SU2014. This would also be appropriate for SU8, correct?
-
Yes, v8, v2013 and v2014
Install in all versions to get the full benefit of the bundles going forward
-
not sure if this has been brought up -
is there a way to have it so that when you disable an extension - it will also disable the plugin? Sometimes they names are different and its difficult to find an extension and its corresponding plugin... or anyway it can be frustrating. -
Whilst autoinstalling v2.6 in SU2013, my Comodo Security popped up twice wanting to partially sandbox a VBS script with a numerical name.
The two files are no longer in the "Temp/SCF" folder.
Is this normal ?
-
Perfectly
-
v 2.6.0
On SketchUp v8 upon starting I get in the console:
%(#004000)[(eval):3119: warning: parenthesize argument(s) for future version (eval):3142: warning: parenthesize argument(s) for future version]On ALL versions 8 .. 14 upon starting I have do deal with multiple VBS sandbox popups, and new entries into my Comodo sandbox file list (which don't exist.)
(1) It is a major PITA.
(2) The VBS file names could have been something to indicate they belong to the SCF Plugin Store extension (instead of some meaningless number.)
-
I'm not familiar with the VBS additions in this release except that they are necessary for older SU versions.
I think TIG will be able to shed more light on your alerts.
We're they occurring on 2.5.2 beta?
-
No I did not see them occurring before.
I will have to turn the extension off, and only use it "on demand".
-
Cool
Sent from my iPad
-
We had some reports about vbs warnings in earlier beta tests but code adjustments were made and there were no further reports.
I am surprised about the 'parenthesize' warning in v8 - I can't think of any arguments passed in this code-set without () ?
Can't you set up an 'exception' for your over zealous 'Commodo' security - to skip vbs files, 'by folder' [.../Temp/SCF] ?
http://help.comodo.com/topic-72-1-451-4758-.html
shows examples using will-cards etc.
So a pattern something like*\Temp\SCF\*.vbsshould work ?These vbs will always run in v8/2013...
The SCFapi in v2014 can use Ruby2 [open-uri etc] for most of it 'communications', but earlier versions rely on vbs scripts using 'XMLHTTP' etc on PC [and .command using 'curl' for MAC].
These tiny vbs scripts are written to the .../Temp/SCF folder to ping data-packets to the SCF server and sometimes receive a response.
These scripts are named "f_nnnnnnn.vbs" where the "nnnnnnn|" is a random integer.
This is to ensure separation between several such pings that might run all but contemporaneously.
Any txt file they might make to hold any received data has a matching name.
On the creation of the txt file the data is read and the two files are deleted a few ms later.
That is why they no longer exist when you look for them.
In case of a rare 'left over' file remaining, on load the SCFapi also purges the ...Temp/SCF folder.Other vbs files are used by other modules to extract the plugin files etc from RBZ archives [renamed ZIP] where the destination folder is not the default Plugins folder [i.e. a custom-plugins folder has been added to the $:]
So even if you disable the SCFapi from loading you will get continuing vbs nags when installing into custom=plugins folders...
-
No tried 6 ways to Sunday to setup exclusions. Does not work as advertised.
Like I say... I only heed SCF Tools when manipulating plugins or extensions.
I'll turn it off.
-
@Dan
You are the only user to report these issues...
I cannot believe it is insoluble
Advertisement