Anyone had this error before?
-
I just got this error when I was trying to change the segment value of an arc (changing from 7 to 24).
Anyone ever had this before??
-
I have never seen that. After you clicked ok, did Google give you a means to contact them? Usually the only way I am offered a reach to them is through a Bugsplat report. It is usually after applying multiple plugins.
-
Well the funny thing is that after I clicked OK the same window popped up so I clicked OK again and nothing happened, the window just disappeared...
could this be some hidden easter egg??
Its the weirdest thing ive ever seen and it almost feels comical or just for fun (like the Google images for Christmas, Easter and so forth...)
-
Here is a bug reporting page:
http://support.google.com/sketchup/bin/request.py?contact_type=bugIndeed a strange error report. I am moving the topic to the SketchUp Bugs subforum...
-
Do you have the model to post?
At my office we have a collection of error messages - but never seen that one. Think you hit the jackpot. Ask them to send a t-shirt for triggering what should never happen.
-
I would love a t-shirt! thats a great idea
I still do have the model however I doubt my company would let me release it...
All I had done was import a .dwg file to model from, I was cleaning it up and was changing the segments of the arc (7 to 24) and that's when I had the error.
After I couldn't change it I restarted SketchUp and I was able to change the segment value.I have not been able to recreate the error since, would love to to find out what was happening though.
-
I had this one happen awhile back. ( I don't remember exactly when, but in the last month and a half sometime.) Like with you, it disappeared and went away never to be seen again; so, I didn't worry about it, and chalked it up to some bored programmer building in some wierd easter egg. You're not alone, but at least it seems to be a benevolent wtf bug
Cathryn
-
It looks like an optimized assert. In performance critical code you let the assert statements compile only for the debug build, but you may still leave some assert statements to be optimized, to aid debugging some big case or long process, then sometimes the sw engineer forgets and its slips to the release build. It happens.
-
well i did send in an error report and i think i asked for a t-shirt but have not heard back from them yet.
im still holding onto hope that ill get some sort of reply
Advertisement