Sorry, but it is unlikely that we would support that behavior. The add-in is written as a custom IV command, and as such has rules on how it can operate.

When editing Custom Properties in a drawing, specifically in a titleblock, the values do not update upon exiting the user window of ipropwiz. It is only after a save do these values update. This is contrary to the behavior of v2.

Neil,

The lists get sorted. This may or may not be desirable.


For instance when I'm entering the allowable scales, they are

2:1
FULL
1/2
1/4
1/8
1" = 1'-0"
1/2" = 1'-0"

However, once in the user interface, the list looks like:
1" = 1'-0"
1/2
1/2" = 1'-0"
1/4
1/4" = 1'-0"
and so on . . .

Can a checkbox be added to choose between list sorting or not?

Neil,

As I click down thru the interface, accessing lists with the dropdown, I must first click on the cell, then a second time to drop the list down.

I know we're getting nitpicky here now, but it would reduce mouseclicks by 50% if one could click on the expected location of the dropdown arrow in the cell and the dropdown immediately open.

This was the behavior of v2. Sorry to keep harking back to a bygone version.

Just wanted to let you know that, while in the Drawing Manager, once properties are edited, clicking on Apply does not apply values in the titleblock . . .

Neil,

It appears that, while editing a part in an assembly, one can not use the measure tool with iPropWiz open. This was possible in v2 (there's that v2 thing again ).

Yeah that's definitely a bummer not being able to measure with iPropWiz open. We gotta get that back. It doesn't even work when you're in the part itself.

If you have the "Comments" field in the interface it produces a drop down memo field box to fill - this is good.

However, the keystroke to move on whilst in Autodesk products is Ctrl-Enter.

It would be beneficial if the user could move down thru the fields as is, by pressing Enter. And when the user is ready to move from the memo fields by pressing the expected keystroke - Ctrl-Enter.

As long as we're editing iPart children and CC family member properties, why can't we edit them in Single Select mode whilst in an assembly? Perhaps there is an easy way around this limitation.

When view the a component's properties, it would be beneficial to have a visual cue as to which custom properties are non-existent in the component. This was . . . . wait for it . . . . like this in V2.

When even in a sketch of a part, why not allow the user to run iPropWiz. This, along with measuring with iPropWiz open would restore a lot of the flexibility that . . . V2 had to offer (sorry just had to . . .)

Jerry,

Based on the way that iPropWiz 2009+ is constructed, there will be some things that it will not be able to do when compared with V2. We'll do our best to overcome what we can, but no promises.

Keep 'em coming.

Neil

You bet Neil. I suspected as such, but not knowing what the source code can and cannot do, I can only point these things up. I understand where the 2 programs are actually different at the core.

It would be helpful to be able to access iPropWiz whilst in a flat pattern AND be able to access the measure tool as well.

Ok I finally figured out what was bothering me about the interface in user mode.

The checkboxes to the right signifying:
- Required value
- Custom property

They really shouldn't be checkboxes in my opinion, because you can't check or uncheck them.

Small point really, but they should be something besides a check box, I don't know it doesn't really matter.