I'm currently working on the next update to iPropWiz. We've had a number of user requested enhancements that may be included, but it's not too late to get your wishes in.

Please reply to this thread if you have something you'd like to see but you haven't posted it before, or emailed it to us outside the forum (we've got all those under consideration).

Thanks,
Neil

Oddly enough I came on with the express intentions of doing just such a thing. I wasn't aware of this thread so here goes . . . .


How about a checkbox to save the thumbnail of the current view?

Another wish would be to have the ability to add a "non-property" textual row in the interface, and be able to add separators as well. This way you could divide up your properties into logical groups and also add a row that you could define a group of properties.

In our case there are 4 properties that are used in an expression, and these 4 properties are a small group in their own right. To be able to add a separator line to distinguish these 4 properties would add a visual cue to the user, and allow the admin to put a reminder of what should go in the properties.

When you deselect "Replace part number with file name", the checkbox option appears to remain anyway.

Either:
1) make this option work correctly, or
2) make it so that it replaces the browser and window header values as well. Currently if you replace the part number with the file name, it does neither of these.

Neil, I still believe it would be more intuitive if the program were consistent in providing a RMB --> "Edit in iPropWiz" context sensitive menu entry both in the Assembly environment and the Drawing manager.

In this way the user doesn't have to be trained to "do this when you're in a drawing, but when you're in an assembly, do this instead."

What about a row of configurable ASCII code symbols, and the option to show the row or not (for those who don't like this idea).

i.e.

Further to this - in regards to the selection workflow - it would be beneficial if ipropwiz could conform to the selection made in the browser or graphics area, be it:
- a part, selected via "Part Priority"
- a component (presumably a part or assembly), selected via "Component Priority"
- any combination of parts or assemblies selected by the user.

As is, selecting "Single Select" in the current interface, forces the user to a "Part Select" mode, and so they cannot select a subassembly. In other words, the Single Select mode - while providing a way to edit a part's property (one part at a time) - is limited in functionality and, IMHO could be replaced with a more intuitive workflow of selecting a set, then RMB --> Edit in IPROPWIZ.

I understand the intent of "Single Select".

It seems that, even if the option to "Replace part number with file name" is checked in the setup menu, the part number in custom parts made from Content Center (i.e. tube lengths) is not editable. If the field is empty, leaving the option "Replace .. . . " results in an exclamation point in the field for part number. Hitting Apply gives no relief. On the other hand, if the field has a value which does not match the file name, the value in the part number field is not altered.

This is for a custom part made from Content Center. Note that I have altered the "part number" value in the Content Center family so that it is intentionally not linked to Project.Part Number, so that CC will not try to populate the Project.Part Number field every time the user changes the size of the part via the "Change Size" interface.

I can provide sample parts at your request.

I should add that I have a macro called "SetPartNumberToFileName" already, which performs well, so I have another way of doing this outside iPropWiz. If it turns out to be too much of a challenge to correct this issue (and that of synchronizing the browser name and window title name to part number), then at least the check box and option to "Replace part number with file name" should be able to be removed entirely from the user interface via Ipropwiz setup, so that the user doesn't see a checkbox which does not always work. We make extensive use of Content Center as a generator for custom structural (channel, angle, flats, tubes) parts.

Thanks for the feedback Jerry. No promises, but we'll look to include these if possible / practical.

The non-property row or separator would not be practical. We use a grid that can be sorted via column which makes this impractical. We might be able to indicate that a property participates in one or more expression(s).

We've seen a couple of glitches with part number = file name, we'll look into fixing this. Please send a custom CC part for testing, no promises as to what we might be able to do.

I like the idea for symbols (diameter, etc).

I see. I understand. An indicator would be good visual cue.



You've got mail.



Good. I'll keep beating away at it. Thanks for your consideration. An excellent tool.

Neil,

I just wanted to make sure you were clear on this thing about the Set Part Number checkbox being displayed. If I'm not mistaken, the version 2 of the tool gave you the choice of actually displaying this checkbox in the user interface. Since the tool did not function properly, I had the option of not displaying the checkbox. The way it behaves here in version 4 is to establish a default only of whether or not the box is checked.

I hope that clarifies the situation.

Neil,

Not sure which way you are heading with this and I think the Single Select is a decent method of editing props of a part in an assembly, although I think the RMB method I suggested is better

But if that is not the direction you are going with it and the Single Select button is here to stay, then maybe add a "Component Select" check box as well.

Or maybe a radio button to choose between
* Current document
* Part Select
* Component Select

Just throwing out ideas.

Just so there is a workflow available to edit parts _AND_ subassemblies within an assembly. That's the main concern I believe I have.

You can switch between component and part selection. During single select, right-click the window background. As with IV, component selection is restricted to first level sub assemblies.

ohhh . . . IOW, RTFM ;-P

In the immortal words of Emily Litella . . "nevermind".

Too bad the interface couldn't be persistent and aware of the current document. In this way a user could open whatever document, or switch between documents and the iPropWiz interface would display the properties of the Active document. I see that iPropWiz can remain open, allowing the user to measure and what not - this is a good thing.

I would imagine the above scenario would be a bit conflicting with the quick select tool. I'm not sure how the two workflows could be reconciled. This is just coming from a guy who just started using V4, so bear with me if I just haven't been aclimatized to the workflow, asking for unnecessary or contrary workflows.