I'm asking around the office. We don't have too many people who use a Wacom regularly w/SU though....I'll see what I can find out though.
Chris
I'm asking around the office. We don't have too many people who use a Wacom regularly w/SU though....I'll see what I can find out though.
Chris
Not at this point. It would be great if it would do it, but its more than I will be able to implement soon.
It also will delete faces occasionally if they are ill-formed. This happens most often when working with geometry imported from other software from what I've seen.
@krisidious said:
He never did part 3? what a bastard...
Seriously!
Glad he doesn't visit the forums anymore...''
Nope, not fixed. I have not seen any way around it at this point.
Wow, I don't have all the shaving progress shots - but I do have a cleanly shaven face.
I'll post a pic when I can.
@gaieus said:
@solo said:
Next a car running on water only?
Please, no. Then water will be as expensive as oil!
Its already got it beat:
@tig said:
The two entities transform methods will affect instances/groups, faces, edges and vertices, but NOT points.
Wow, its beena while since I used those methods, apparently I had forgotten that. I guess I'm transforming vertices in my script then.
Sorry for the bad advice
Try these two options:
entiites.transform_entities
entities.transform_by_vectors
http://www.sketchup.com/intl/en/developer/docs/ourdoc/entities.php#transform_entities
http://www.sketchup.com/intl/en/developer/docs/ourdoc/entities.php#transform_entities
@slbaumgartner said:
OK, this just keeps getting weirder On my Mavericks Mac, TIG.remote works just fine after the typo is corrected. What the bleep is going on????
That is what we're seeing here as well Steve. From what we're seeing this all boils down to either having not included the allow_actions_from_host either not being implemented at all, or having been implemented with bad syntax (a url vs a domain string), or a typo.
It appears no other OS, other than Mavericks, actually pays any attention to this method. That is what my quick testing is showing. I'm very open to hear about exceptions to these findings or issues that might be different.
Chris
I'll jump in now, I concur that it all appears to be related to the dlg.allow_actions_from_host method. I think its possible that Win and OS have not actually been honoring that method. But Mavericks now suddenly does.
So if people are not using it, it will dis-allow certain actions with remote websites and throw that error.
If you do use it (which you really should now), make sure you have the syntax correct. You should be giving it a domain, not a url. example: dlg.allow_actions_from_host("http://www.sketchup.com")
is not correct, it should be dlg.allow_actions_from_host"www.sketchup.com"
Now I'm curious to know if that is enough to fix all/any of the problems, or are people still seeing other problems?
Chris
Yeah, the developer's forum is a good place for it I think.
Still looking into it on our end, nothing new to add to the discussion yet.
Chris
Oh, TIG already responded. Yes, this is an odd one.
Thanks John - I think that is the typo in question.
As to why it works in all other OS's except for Mavericks.....that I don't know.
Weird, I'll try to test the version on the warehouse. The one on the EW should not need progressbar though. I removed that dependency from that version. But maybe I introduced a bug in the process
RE: the test file used here - we found that the test file has a typo in it, and that is why the remote download is failing in that script. It actually is trying to reach an invalid URL
So unfortunately that isn't showing any errors once the typo is corrected.
We're still looking into this.
If this system is entirely under your control, it would be easy to include all the geometry in the template model. Then when the user opens a new model, all those components are there without any possibility of being undone.
As a Pro user you can contact SketchUp help and provide your license info and they can help you fix it quickly.
Chris
I've got nothing to add at this point, but I did want to chime in just to make sure everyone knows that we are looking into this issue as best we can also and working directly with some of the developers who have emailed us already. We'll post here as soon as we know anything useful. Thanks,
Chris