thx!

It is a good idea, and will be put to use. Something like the following is how it might fit into what I have already: Animation.add('fog', start_value, end_value, duration (frames or seconds), easing_function) Animation.add (...) Animation.play

@jim said: I am getting the same sort of increasing slow-downs as Chris was asking about. The time between each pause increase the more geometry is added. Oops, not quite. I was creating and exploding groups when I wrote the above. When I just add plain geometry, the timeout appears to work alright. But... the pause between when my dialog is visible and when it actually becomes click-able is getting longer. I think I'm beating a dead horse.

@jim said: With it, you can do this (abort a long-running operation) Oh yeah, I'm definitely going to try to tie this in to start_operation. That way, I can set a single timeout limit for all scripts transparently.

Dunno if we can repackage it... but looking at them just reminded me of this project again and I had some ideas flying past.

i am a regular user of these texture program...

@cphillips said: I have had good luck with Firebug lite. http://getfirebug.com/lite.html Ah! Firebug is one of my fav Firefox extensions. This Lite version looks very interesting!

Thanks Whaat.

Very strange, this unavailability, indeed...

It wasn't the 3d warehouse dialog, but a webdialog I put together with some small functions for a specific task. One of the tasks was selecting and replacing a whole lot of instances. The dialog went away after I wrapped some of my functions in start_operation/commit_operation.

Thanks Jim

Well the DOM (document object model) of a HTML page is rooted from an instance of document and everything hangs off that. If you have multiple WebDialogs, you have multiple DOMs, each with their own parts hierarchy which have names which are 'within' the scope of just that document. So, Google "DOM" for more info, but its basically just a hierarchy of named & typed parts. Adam

@adamb said: But thats correct behavior if I unwind an operation to just before the Tool was used..No? Nah. Not IMO. I find it very annoying. I want to keep the focus on the viewport.

Jim withdrew the majority of his plugins. It may not be available any longer.

Thanks Adam, I was actually using the following: str.gsub!(/\\/, '\\\\') But I think simply changing it to '/' is a better solution, and will modify inputbox.rb I suppose it's possible for someone to want to use \ for some other string, though. I'm also escaping double-quotes: str.gsub!(/"/, '\"') Thanks.

I'm pretty sure the only way to effect an instance without effecting the definition is just the Transform. But that will just effect the instance as a whole. You can't reverse the faces (I don't think) without interacting with the actual geometry, thus changing the definition.

@solo said: How about the ability when searching to avoid the 500 pages of manufactures items that look all the same, have them grouped within the results with one model that will take you to the collection instead of hunting for those results to end and the item you are looking for to start?. (sorry best description I could think of) Well, you can use the 3D Warehouse advanced search options in the browser, such as searching for: "faucet author:-kohler" or more simply: "faucet -kohler" might work as well. Not an ideal solution, but sometimes helpful. Maybe someone could write up a short tutorial on advanced searching in the Component Browser?

@remus said: @gaieus said: "Duh" +1 Its strange how you just dont notice these things after a while. Maybe the triangles are another solution to a problem that really doesn't exist. They don't disturb me, either, but if the feature disappeared, I doubt if I would notice. Anssi

@chris fullmer said: I don't quite understand what that means. What is bitwise? Think in binary, then compare them column for column. It's a logical, bit-to-bit comparison. 5 in binary is 101 6 in binary is 110 5 & 6 is; logical AND each column (bit position) Columns ________________ | 1 | 0 | 1 <- decimal 5 | and | and | and | 1 | 1 | 0 <- decimal 6 ================= 1 0 0 so 101 & 110 = 100 <- decimal 4 The masks are constants, which are set to some convenient values: # I just made these up 001 = CONSTRAIN_MASK 010 = ALT_MASK 100 = COPY_MASK So if the flag is decimal value 7: 111 <- decimal 7 In order to check the CONSTRAIN_MASK, you logical AND the CONSTRAIN_MASK with the flag value: 111 <- flag value decimal 7 & 001 <- contain mask constant ====== 001 <- CONSTRAIN_MASK set true or in real ruby as Thomas wrote; contrain_key_down = ((flags & CONSTRAIN_MODIFIER_MASK) == CONSTRAIN_MODIFIER_MASK) copy_key_down = ((flags & COPY_MODIFIER_MASK) == COPY_MODIFIER_MASK) alt_key_down = ((flags & ALT_MODIFIER_MASK) == ALT_MODIFIER_MASK) Although Adam B might know a clever way to decode them all in one elegant statement.