Wallace White
Usenet Archive
- Joined
- Dec 8, 2000
- Messages
- 52
- Reaction score
- 0
One of my least favorite tasks is updating the revision block on a Pro/E drawing. Insert row, enter text, change text size, wrap text, edit row height for newly wrapped text... and repeat for multi-sheet drawings.
Anyone know a quicker way to manage a revision table / block?
I used to use SolidWorks, which allowed Excel OLE objects to be inserted in drawings. This at least avoided the nuisance of using Pro/E tables. Pro/E can insert OLE objects but, frustratingly, cannot plot them except to the "MS Plotter," which I don't even see.
I have a dream of putting all revision information in the part's parameters (esp. since we don't use "location" on our rev blocks). I prefer to keep all info in the part anyway. But I can't think of how to do that without having the rev block preset to a large number of rows; for some unlucky parts, that won't be enough, either.
What I'd really like is parameter arrays (e.g. rev[x], rev_date[x], rev_note[x]) and a way of specifying repeat regions in the rev block, just like BOM tables, that use all records in the array.
I'd love to hear other ideas on this.
Thanks,
Wallace
Anyone know a quicker way to manage a revision table / block?
I used to use SolidWorks, which allowed Excel OLE objects to be inserted in drawings. This at least avoided the nuisance of using Pro/E tables. Pro/E can insert OLE objects but, frustratingly, cannot plot them except to the "MS Plotter," which I don't even see.
I have a dream of putting all revision information in the part's parameters (esp. since we don't use "location" on our rev blocks). I prefer to keep all info in the part anyway. But I can't think of how to do that without having the rev block preset to a large number of rows; for some unlucky parts, that won't be enough, either.
What I'd really like is parameter arrays (e.g. rev[x], rev_date[x], rev_note[x]) and a way of specifying repeat regions in the rev block, just like BOM tables, that use all records in the array.
I'd love to hear other ideas on this.
Thanks,
Wallace