Topics created by tomot

https://sketchucation.com/forums/viewtopic.php?f=179&t=69981&p=641021#p640940 😉

Your current 'circle' code only draws some edges [all be it that they are in the form of circles].
Use e.g.
edges=ents.add_circle(@pt1, @vec3, @dia, 24)
Then make a face for one of those edges...
ents.find_faces(edges[0]) face=edges[0].faces[0]
Then add a material to the 'face'...

Of course this is very simplistic...
e.g. if your circles might overlap etc not all edges might get a face, so then you probably need to make each circle/face inside its own group in turn, at least until you have finished making/painting it etc, after which exploding the temp-group can put the faces back into the desired entities-context...

Here is the bottom line in the .ZIP to .RBZ saga

My current version of Winrar 5.31 (64-bit) ....failed to faithfully do a proper .zip conversion.

TIG informed me how one script I sent him was able to be installed while the other was not.
How is this possible?
That lead me to investigate what had happens to WinRar, which I have used for .rar .zip and password protect files since the early 2000's

I attached one of my very old XP HDD's via a none sata to usb connection to my PC. And there it was, an old copy of Winrar 3.71

I used the old Winrar 3.71 to make a new zip file renamed .zip to .rbz installed the .rbz voila! ... it installs via the dreaded Installation Manager!

I admit I'm a so learner, this is not the first time I have regretted getting on that bloody upgrade treadmill. I can hardly wait for SU 2018 😞

As TIG said, add_line was a deviance from what the norm. I think it got named like that because in the UI you have the "Line Tool". But in the API this is an unfortunate inconsistency.

And as Dan mentioned, please report documentation issues in the GitHub repo.

I queued up some cleanup to the followme method:

2016-12-21_13h57_14.png

@unknownuser said:

I have no idea how you determine what @ptw1616 is but another option might be creating an array of the locations like this

All the points are per-determined in my script. They relate to the user selected area.
Various combination of points make a pattern of lights the user can choose from in the Light Array Type Dialog Box.
Your understanding of Ruby has helped me tremendously. Furthermore I did not realize the importance of the last "}" .....which I originally thought might have been a typo........ Yikes!!!

Change the precision setting to 1/32 and it should readjust.

Precision.JPG

@dan rathbun said:

I remember that the layer name of 0 was changed from language localized names to "Layer0" for all language editions at some point. (We would think the validity check would fix this, in newer SketchUp versions.)

Perhaps unicode characters are causing issues in layer names ?

I'm wondering if the following code I'm using might be the cause?

layers=model.layers layers.add (@frame) activelayer=model.active_layer=layers[@frame] layer=model.active_layer #code that places stuff on layer frame #goes here #at the end of this routine I reset layer # Reset layer back to default layer [0] layers = model.layers activelayer = model.active_layer=layers[0] layer = model.active_layer

@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]!

@tig said:

Never include a space between the method and the opening parenthesis that is enclosing its argument[s]...

I was going to tattoo that statement on my arm, but my Wife wont let me. 😄

Regardless, I have often wondered what goes through the mind of those that write
computer languages. What fantasy world do they live in? It would not be very easy to read
a sentence without spaces between words, would it?

👍 👍

@numerobis said:

Nice one!
Very clear and unemotional. Concentrating on the most obvious facts.

The photoshopped video tapes of the pentagon cam were new to me.

a shorter version... 😉

http://www.youtube.com/watch?v=RGxMoMFAez4

👍
We all know this, but the real question is - Why it was done like they actually wanted everybody to know? In the Hollywood land this set up was amateur job. Why?
I think this was on purpose - a public intimidation tactic. No one is free and safe in the land where government can do this kind of thing to people, without any consequence. This was a public declaration of new level of totalitarianism.

Try

point = Geom.intersect_line_line(edge1.line, edge2.line)

You either get a point or nil if the two 'lines' don't intersect.
Unlike an 'edge', a 'line' is infinite, so two 'edges' might not physically intersect even though their 'lines' do.
If you get a point you can then test if it actually falls on an end point of an edge
point == edge1.start.position point == edge2.end.position point == edge1.start.position point == edge2.end.position
where true shows it is at a vertex
AND if the point falls between the start/end of each edge, the test is...
point.vector_to(edge1.start.position) == point.vector_to(edge1.end.position) point.vector_to(edge2.start.position) == point.vector_to(edge2.end.position)
Note that getting true means that the point is not physically on the edge because the vectors are both in the same direction, and false means that the point is on the edge and between the start/end...

@aerilius said:

There are many ways to create strings:
string concatenation:
90.to_s + " degrees" # slow because it creates a new third string object
string appending:
90.to_s << " degrees" # faster because it adds the second string into the first
string interpolation:
"#{90} degrees"

Note that string interpolation is the fastest. (And reads easier IMO)

@tig said:

So ac=**63.0** and then in the equation ad = Math.asin(db * Math.sin(ac**.degrees**) / dc).radians
Now 'ad' is in degrees again, so when you Math equation processes it uses ad.degrees

I was not confused between degrees and radians. Its the same way angles are treated in many languages, I'm quite familiar having written AutoLisp routines years ago, which also uses degrees and radians. Its more about me learning how to write the same code in Ruby
.........I finally see in your example how .degrees gets added, its really simple once I saw your example. 🎉

@tomot said:

The interesting thing about Bitcoin is that it’s made everybody start to talk about what money is, and why money has any value. If you think about it, since 1971, when the US came off the gold standard, the dollar hasn’t been linked to gold, it hasn’t been linked to anything. You have a piece of paper which says ‘In God we trust’, it does not say 'In Government we trust'. That piece of paper is absolutely meaningless. You’re putting your trust into banks and central authorities. The Federal Reserve which prints the dollar has nothing to do with anything Federal. Its simply a private banking corporation, which has the authority to print the dollar for the Federal Government. The Fed is also very busy these days printing more paper.

Bitcoin is a whole new idea about what money is, money is basically regulated by network and by the people.

Recently Central banks around the world are looking at the development of Bitcoin with a lot of fear, and not just central banks, but the traditional banking system as a whole. Bitcoin has been around since 2008. Regulators didn’t pay any attention to it, they dismissed it as some sort of monopoly money. But things are changing for Bitcoin.

Funny thing is, the dollar you use daily, no longer supported by gold, is also monopoly money, ... is it not?

Speaking of Gold; Germany recently wanted to repatriate their gold stored in US vaults
http://nsnbc.me/2013/04/18/federal-reserve-refuses-to-submit-to-an-audit-of-germanys-gold-held-in-u-s-vaults-2/

Which raises the question where is the Gold? ...is paper backed by nothing, nothing more than the ultimate Ponzi scheme?....do you care?.

I would hardly call U.S. money absolutely meaningless. If you truly feel that way, you're more than welcome mail me all your money, and I'll take care of that meaningless paper for you.

Contrary to popular belief, the Federal Reserve does not print money. U.S. currency is printed and minted by the Bureau of Engraving and Printing (BEP) under the Department of the Treasury.

"In God We Trust" is just a logo. Paper money also has the words "THIS NOTE IS LEGAL TENDER FOR ALL DEBTS PUBLIC AND PRIVATE" and is signed by both the Treasurer of the United States and the Secretary of the Treasury. The value of U.S. currency is backed by the full faith and credit of the United States.

Your assertion that the Federal Reserve is a private banking corporation or that it has nothing to do with anything Federal is wrong. The Federal Reserve System (aka the Federal Reserve, the Fed), the central banking system of the U.S., derives it's authority through The Federal Reserve Act of 1923 and subsequent congressional statutes, and is subject to congressional oversight. The U.S. Congress established three key objectives for monetary policy in the Federal Reserve Act: Maximum employment, stable prices, and moderate long-term interest rates. Its duties have expanded over the years, and today, according to official Federal Reserve documentation, include conducting the nation's monetary policy, supervising and regulating banking institutions, maintaining the stability of the financial system and providing financial services to depository institutions, the U.S. government, and foreign official institutions.

I checked your extensions to invoker c#from ruby at https://github.com/icehuli/suWpfExt.
I used to use win32ole to invoke my c# extensions. But since SU2014 and ruby 2.0I could not get anything up and running yet, either icehuli extension or my win32ole calls...

Understood! 😉