I have the 27" iMac and for me it works great with Sketchup. but as I don't do much modeling but more programming I cannot say much.
I can test some .skp if you want with Test.time_display
I have the 27" iMac and for me it works great with Sketchup. but as I don't do much modeling but more programming I cannot say much.
I can test some .skp if you want with Test.time_display
Adam: yay, finally animated textures are back in Sketchup ! almost 3 years after my proof of concept and it works great without hacks.
love LightUp player, can you make an iPad version as well ? ps. nice password on .luca files.
it was ok, the command line needs the .rb file that needs to be executed in the Sketchup context.
@al hart said:
I think it would be fun to see how they are doing it.
I put a link in my previous post where you can see lots of protections and how they are defeated (see solutions).
there are a lot of bogus links (e.g. Podium download 700mb when the entire setup is 2mb) full of crap malware, so better wear protection
@al hart said:
Even though they can crack the next one, at least I would slow things down a bit.
you will only slow down your product development. they have a lot more experience in this and more dedication and can break protections that are lot stronger than whatever you can come up to (if it is possible to crack 768-bit RSA, imagine cracking your simple encryption that can have a lot of holes)
"if it works on user machine, it can be cracked" - anonymous cracker
you can play with crackmes and see protections and how they are defeated.
@lbaeyens said:
I don't know why on Mac SU comes with the full Ruby set while on PC only the "core" Ruby components are deployed.
because OSX, not SU, has Ruby preinstalled by default (among other nice things).
I think it is a typo, as it is the ALT key on Mac. tested with a simple tool.
tested on Sketchup.OSX - no crash.
tested on Sketchup.Win inside OSX - crash.
inverted h/w - no crash.
saved as .jpg with high compression - crash.
traced the problem to a memcpy which reference an invalid pointer
@unknownuser said:
Its only the first 3 chapters that are available actually.
the full book is available here with "There are no conditions or restrictions - feel free to download and distribute the PDF as you like. However, objective reviews of the content are always welcome. "
if you look at the Makefile generated via extconf.rb you have
CFLAGS = -fno-common -arch i386 -arch x86_64 -g -Os ...
so you can add/modify for PPC to suit your needs. didn't tried it, so I dont know if it works ok. btw, are there a lot of PPC users to worth the effort ?
Snow Leopard Ruby code (1.8.7);
> puts RUBY_PLATFORM
universal-darwin10.0
Sketchup Ruby (1.8.5);
> RUBY_PLATFORM
i686-darwin8.10.1
Terminal code;
> file /usr/bin/ruby
/usr/bin/ruby; Mach-O universal binary with 3 architectures
/usr/bin/ruby (for architecture x86_64); Mach-O 64-bit executable x86_64
/usr/bin/ruby (for architecture i386); Mach-O executable i386
/usr/bin/ruby (for architecture ppc7400); Mach-O executable ppc
Some time ago i liked 4 spaces ident, but nowadays i am on tab 4 - easy to jump to 2 if the code is too wide, smaller filesize.
using RDE autoformat works great on my code and 'alien' code so I can don't care about identing much when I code.
wished I had this book 6 years ago, but I am glad that now I gave a hand (review part) in helping future SketchUp Ruby coders.
recommended.
safer IMHO. also easier on the eye in the source code.
ALLOC* are just macros that use xmalloc which is a malloc with a if condition for memory exceeded. (I use ALLOC* with free in my code btw)
thomthom: yes
when in doubt always try it. faster than posting a question on forum
added suext6.ppj in SUExt dir on github. it should work now. I use PellesC 5 and something was changed in 6 that made that error.
just double click on suext.ppj and it will open in PellesC IDE and then you can Project | Build and you will get a suext.so ready to use
@thomthom said:
This would leave me with
arr
being an Ruby Array representing the vector, right?
right
@thomthom said:
I see there are
rb_each
andrb_iterate
- should one use ruby iterators to loop through Ruby Arrays in C? Or can one use regular C loops?
definitely rb_ functions as you are manipulating an array of pointers (VALUE objects)