[Plugin] 2D Tools v5.3 20120929

[lapx]

Can 2d tools work for any plane? It would be nice if one could lock the 2d tools to any plane.Is this what surface tools tries to do? You should be able to lock your plane to draw in 2d on any surface. Then any drawing would be on the surface as 2d. i know it works on in the xy plane.
It would be handy if it worked on surface of any set plane.

[TIG]

Can 2d tools work for any plane? It would be nice if one could lock the 2d tools to any plane.Is this what surface tools tries to do? You should be able to lock your plane to draw in 2d on any surface. Then any drawing would be on the surface as 2d. i know it works on in the xy plane.
It would be handy if it worked on surface of any set plane.

Some tools do work in any plane [e.g. Fillet].
You can reset the z-height for many other 2dTools.
Fredo's 'Tools on Surface' will also draw most basic shapes on any surface too...
With the advent of LayOut further development of 2dTools is unlikely...

[micione]

I found the plugin that creates a conflict with 2D Tools / fillet: it is "Driving Dimension" by LEDAS.
Now everything works fine.
Thank you.
Roberto

[TIG]

I found the plugin that creates a conflict with 2D Tools / fillet: it is "Driving Dimension" by LEDAS.
Now everything works fine.
Thank you.
Roberto

Sorry I didn't spot the ldd.rbs in the list. It is one of the tools implicated in a lot of clashes with legit tools because I suspect that it ill-advisedly changes some base class/methods for groups. I have previously written to the author asking them to fix it.
Note that some other similarly implicated scripts include SketchyPhysics, Matchbox, SunTools[?] etc

[micione]

TIG,
thanks again.
Maybe we should create a "black list" of all the scripts that create conflict.
And make it visible on the forum.
I also write to LEDAS for this problem.
I must warn FREDO6, that his tool "additionalplugin foder" creates
conflict with other plugins? (For example with "instant roof" and FollowMe rotate ")
regards,
Roberto

[micione]

TIG,
sorry but I can not send and receive private messages by using
the user control panel.
What should I do to activate this feature?
my username: micione
my email: robertopadulazzi @ alice.it
My real name: Roberto

[TIG]

If you click on this

Capture.PNG

and then this

1.PNG

you should get a new blank post, fill it in with title, text.attachments and recipients...
If you click on the PM icon below a post's author's details/avatar

2.PNG

, it will open a new post, with the same title and the recipient filled in

3.PNG

What is your difficulty precisely ?

[micione]

TIG,
I found the problem.
This is Google Chrome / instant translator of the page.
By disabling this feature, it seems all right.
Thank you.
Roberto

[micione]

TIG,
I talked to "LEDAS" the problem of "driving dimension" that creates conflicts
with other plugins (specifically with 2D Tools).
I responded thus:

Ilya Tatarnikov 2012-05-11 05:58 UTC
Hello Roberto,

We confirm the problem and trying to investigate reasons and find solution.
For more efficient work I'm recommending you to contact also to 2Dtools development team.
They maybe got such request earlier and find some solution.

--
best regards,
Ilya Tatarnikov

[TIG]

It is not just my tools... but several tools made by others, that use legitimate Sketchup API class/methods [usually about 'groups'] that ought to 'return' certain values, but which LEDAS's tool overwrite ill-advisedly, thereby breaking several legit tools to enable his own !
I have tried to circumvent several standard 'group' methods to avoid clashes like this [SketchyPhysics and others also do similar screw ups!], but there is a limit to what I can do. If LEDAS's code was not compiled it would be easy to find the issues, I have PM'd him about this ages ago, but I think he is just being obdurate, because his code works, 'so screw everyone else...'

[thomthom]

For more efficient work I'm recommending you to contact also to 2Dtools development team.
They maybe got such request earlier and find some solution.

Bah! Humbug!
Overriding the base classes in SketchUp is a big no-no. Leaving it to others is just extra bad manners!

[thomthom]

Registrationware as well - don't like it when I have to give out my full details just to try a software...

[Dave R]

This subject of the problems Sketchy Physics, Driving Dimensions and others cause comes up frequently. The authors have been approached more than once with requests to fix them but have never done so. It would appear to me that they have no interest in doing so. Perhaps there should be a sticky listing these plugins that are written so they cause plugins that are properly written to fail. A comment could be included to the effect of, "Understand that if you choose to use these plugins, they may cause other plugins to fail. Use these plugins at your own risk."

[thomthom]

I've been looking into LDD - When it's installed pretty much all the base classes is flooded with LDD methods. Even the root Object!!

Object.ancestors
[Object, LDD, Kernel]

An LDD module is added to the Object class.

And just the constants that LDD adds:
LDD.constants
["SKETCH_TOOL", "PI", "GENERAL_CASE_LINES", "LDDEntitiesObserver", "EQUAL_LINES", "PUTS_IN_RUBY_CONSOLE", "CONSTRAINTS_LIMIT", "ENTITY_OBSERVERS", "LDDFaceFaceAngleConstraint", "LDDOptions", "LDD_return_values", "SKETCHUP_VERSION", "LDDVertexVertexDistanceConstraint", "ROTATE_TOOL", "Driving_Dimension", "LDD_constraints_types", "LDDVertexFaceDistanceConstraint", "CAMERA_ZOOM_TOOL", "ARC_TOOL", "LDDModelConstraints", "LDD_constraints_typesVersion_0_2", "Driving_Dimensions_Tool", "LDDFaceInformationForInferredConstraints", "LDDAppObserver", "LDDEdgeEdgeDistanceConstraint", "LDDLabelsObserverForVertex", "LEDAS_DRIVING_DIMENSIONS_BUILD", "INTERSECTING_LINES", "LDDFixationConstraint", "LDDEdgeFaceAngleConstraint", "CAMERA_ORBIT_TOOL", "DRIVING_DIMENSIONS_FIXATION_TOOL_CURSOR", "VERTEX_OBSERVERS", "LDDEdgeLengthConstraint", "LDDModelObserver", "RECTANGLE_TOOL", "LDDPreConstraint", "FULL_LOG", "LDDDrDiTextObserver", "LDDSet", "LDDEmptyConstraint", "DRIVING_DIMENSIONS_CALCULATING_CURSOR", "LDDEdgeEdgePlanarAngleConstraint", "PUSH_PULL_TOOL", "PARALLEL_LINES", "LDDDrDiEntityObserver", "LDDFaceFaceDistanceConstraint", "LDDToolsObserver", "LDD_PRO", "LDDVertexEdgeDistanceConstraint", "MOVE_TOOL", "LEDAS_DRIVING_DIMENSIONS_VERSION", "LDD_DIR", "LDDDataForSketchupModel", "LDDSelectionObserver", "DEG_SIGN", "LDDConstraint", "LDDEdgeFaceDistanceConstraint", "CAMERA_DOLLY_TOOL", "DRIVING_DIMENSIONS_TOOL_CURSOR", "LDDArcCurveRadiusConstraint", "CIRCLE_TOOL", "INTERSECTING_LINES_WITH_COMMON_FACE", "LDDDrDiGroupObserver", "LDDEdgeEdgeAngleConstraint", "LDDObserversHash", "LDDKEY", "OFFSET_TOOL", "Driving_Dimensions_Fixation_Tool"]

Notice that even a PI constant is added - so now it's available to all classes instead of Math::PI. What a mess...

LDD really do not play nicely with the shared SketchUp plugin environment at all!

[chickbiker]

TIG - how does one go about acquiring a copy of your 2D tools? Looks like just the fix I need. Assuming it works with the free version... posting.php?mode=reply&f=323&t=22091#

[mitcorb]

Look at the bottom of the first page of 2D tools thread. At the bottom, see the Attachments box. The plugin is in a zip folder. Right click, save file as.. and place it in your favorite destination folder on your computer. Then unzip it to your Sketchup Plugins Folder.

I don't know why you inserted that link to a Reply panel. At the bottom left of the Reading Window is a Reply button.

[Howard Leslie]

TIG,
I've noticed that the 2d toolset will occasionally crash SU under the following circumstances.......
See attached skp.
Using your 2d Toolset, I'd like to be able to put 2 Fillets on some adjoining linework (3 adjacent lines)
The linework is not all on one plane. (2 horizontal lines, 1 vertical)
.......
first fillet - no problem.
second fillet (on adjoining lines but different plane)- will crash SU
........
Solution - move reqd lines off to one side and fillet, then put lines back in place.
I sometimes use this toolset when working on 3d models (even though it was originally designed for 2d work) - its very useful
........
If you have time and could look into this it would be most appreciated.
.......
Regards
Howard L'

[TIG]

Howard

I can't get it to crash at all !
It fillets the two nodes in turn without an error [@r=1000mm].
Also the order that they are picked has no effect either ?
I'm very puzzled...
What's you SUp version and OS ?

Can anyone else manage to get this to fail ?
If so, how exactly ??
Testers please...

[Michaelv]

No problem here, Mac OS and version 5.1(Mac) of tools.
Tried all combinations of sequences

[Dave R]

I don't think it's TIG's plugin. The first time I opened the file I got a crash before I'd even tried to do anything with any tool. No idea why it crashed. I opened the file a second time and put in fillets with a 1000mm radius on the original set of lines with no trouble.

[Howard Leslie]

TIG,
Thanks very much for your reply
.........
To answer your question:

SU Pro 8.0.11752
Windows Vista c/w Svc Pack 2
(32 bit PC)

Latest version of 2D Tools
Text notes inside the #2d.rb file gives the version as
### v5.0 20100927
..........
Really wierd how nobody else can reproduce this bug splat / behaviour
Possible clash with another Ruby script ???
.......
Howard L'

[Dave R]

Howard, you may have hit the nail on the head. You might try to find out by removing other plugins temporarily and trying the fillets.

[TIG]

As the title-bar says "v5.2" you could also try upgrading to the latest version...

v5.1 20111201 Newly reported glitch fixed with 2dLine, so that now pressing the keyboard '0' when typing in a number on a PC it doesn't mistake for TAB >> Z-height!
v5.2 20120228 2dFillet segment range adjusted to >=2 <=999.

??? I don't think any of these changes are important BUT you never know

[Howard Leslie]

TIG,
The version of 2D Tools that I have installed is from 2D_Tools52.zip.
When I got the bug splats I made sure I had the latest version before reporting any possible bugs.
...........
The text I quoted above was from the notes inside the #2d.rb file.
I shouldn't have quoted this - its a bit misleading - as I see now that there are many *.rb files inside the zip file that you may have updated on the last release - not just the one.
............
If its tricky to track the bug down / reproduce the fault - don't worry about it as I can work round it.
However, if I notice anything else, or any other possible leads I'll report it.
.............
Brilliant plugin by the way
..............
Thanks once again

Howard L'

[Dave R]

Did you try removing the other plugins in the Plugins folder and running just 2D Tools? It doesn't appear to be a bug in the 2D Tools set. If it was, there'd be a large number of complaints and that doesn't seem to be the case.

[ninomayda]

Superb Tool. A "must" to all SKPrs. Attached please find Xcel sheet to assist calculating text size dependant on final presentation (Layout) drawing scales.

[Milo]

Fantastic tools thank you very much !!!

[Helmi]

Thanks for that great tool.

Still one question left: I can't seem to decode NNs/NNx/Rad with the 2D polygon and NNs or Rad with the circle. No matter what i enter there it doesn't seem to affect anything. I tried to rise the segments of the circle but can't seem to get it and couldn't find any docs for that?

Any help would be highly appreciated.

Thanks!

[TIG]

Thanks for that great tool.

Still one question left: I can't seem to decode NNs/NNx/Rad with the 2D polygon and NNs or Rad with the circle. No matter what i enter there it doesn't seem to affect anything. I tried to rise the segments of the circle but can't seem to get it and couldn't find any docs for that?

Any help would be highly appreciated.

Thanks!

Please look at the installed toolset there's a help menu/toolbar item... this opens the file inside the ../Plugins/2Dtools/ folder called '2DtoolsHelp.htm'...
There's detailed explanations about using each tool.
If you want to change the number of sides in a Polygon or Circle [in 2Dtools OR the native-tools] typing 99s changes to 99 segments..., typing in a number e.g. 99 sets the radius to that in 'current units' - you could also type 99mm to set it to that, even if the current units weren't 'mm'...
With 2d Polygons the extra option of typing 99x sets the 'width' across edges rather than across vertices...

[Helmi]

Thanks, TIG. Didn't notice that help menu item. Great work, thanks a lot!