This is related to the previous question about splitting up tables, but it applies to any inserted OLE object. We have some lengthy tables that have to be split up into individual DOORS objects. We want each segment to be entirely visible when viewed in DOORS, as well as when it's exported to a Word document. (We're not actually using the DOORS Export function, but our own publishing script that uses our Word templates. Same result.)
My question is, has anyone come up with a rule of thumb for the ideal size of an inserted OLE object? It can't be taller than the screen when DOORS is in full-screen view, but how much shorter than that does it need to be? It can't be wider than the margins in the final Word document, but what's the maximum width before it starts to be impossible to view in DOORS?
firstgentrekkie - Fri Sep 14 08:43:07 EDT 2012 |
|
Re: Question about inserted OLE objects
kbmurphy - Fri Sep 14 11:38:22 EDT 2012
No offense, but you are doing it wrong.
http://www.baselinesinc.com/?page_id=11&filerepoaction=showpost&filepost_id=14
|
|
Re: Question about inserted OLE objects
firstgentrekkie - Fri Sep 14 12:32:31 EDT 2012 kbmurphy - Fri Sep 14 11:38:22 EDT 2012
No offense, but you are doing it wrong.
http://www.baselinesinc.com/?page_id=11&filerepoaction=showpost&filepost_id=14
Nevertheless, that is our procedure.
|
|
Re: Question about inserted OLE objects
kbmurphy - Fri Sep 14 14:21:45 EDT 2012 firstgentrekkie - Fri Sep 14 12:32:31 EDT 2012
None taken.
Nevertheless, that is our procedure.
|
|
Re: Question about inserted OLE objects
firstgentrekkie - Mon Sep 17 08:15:15 EDT 2012 kbmurphy - Fri Sep 14 14:21:45 EDT 2012
Then my answer is that the ideal size of an OLE object is the same size as the document that will be produced. If you have an a Word OLE object that fits within the margins of an 8.5x11 Word document, and that 8.5x11 is your target size, then you're set.
I don't believe an object of that size is fully viewable on the screen in DOORS. There seems to be a maximum object height that I haven't been able to identify, such that the bottom of the table will get truncated. Not only that, but often if it's not viewable, it seems that it doesn't get printed correctly, either. But full-page, minus margins, is certainly a good starting point.
|
|
Re: Question about inserted OLE objects
kbmurphy - Mon Sep 17 11:54:15 EDT 2012 firstgentrekkie - Mon Sep 17 08:15:15 EDT 2012
"ideal size of an OLE object is the same size as the document that will be produced"
I don't believe an object of that size is fully viewable on the screen in DOORS. There seems to be a maximum object height that I haven't been able to identify, such that the bottom of the table will get truncated. Not only that, but often if it's not viewable, it seems that it doesn't get printed correctly, either. But full-page, minus margins, is certainly a good starting point.
> "ideal size of an OLE object is the same size as the document that will be produced"
This depends solely on your screen resolution.
>
> There seems to be a maximum object height that I haven't been able to identify, such that the bottom of the table will get truncated. Not only that, but often if it's not viewable, it seems that it doesn't get printed correctly, either. But full-page, minus margins, is certainly a good starting point.
Many variables here. This has to do with the margins and paper size of the target Word document. And again, if you're doing it this way, you're doing it wrong (what happens when you've broken a 10-page table into 10 separate OLE Word tables and then have to insert a new row in table 3? You now have to edit 7 tables or maybe even create a new one).
Anyone reading this should use the script I link to above. It's the only way to do this right, 100% of the time, and not have to worry about formatting the document.
|
|
Re: Question about inserted OLE objects
cliff.sadler - Fri Mar 29 14:23:20 EDT 2013
OK, I'd like to take this a bit further. I have a very large table (many columns wide). We have been maintaining the table in Excel because of ease and familiarity of manipulating columns and rows. This table is stored in DOORS in relation to requirements, and is periodically published to Word.
So, typically, I copy the contents of the Excel sheet into a Word document (11x17 Landscape), save that, and insert it as an OLE into its own object. RPE renders it nicely, and all is good. I would like to be able to see the contents of the table in DOORS, however there seems to be a hard limit on the height and width of an inserted OLE object's "render". Do you know of any way to change the max width, and/or max height of an inserted OLE? It looks like the visible limit is what is shown on a Word Export. Even though the page is wider than the OLE table (not hitting margin issues width wise), it will not render past a certain width, both in the DOORS object, and in the Word exported OLE container in the document.
When I run Kevin's ExpandOLE macro, of course it does come in to the document full width and multi-page height. Perhaps it's just a limitation of OLE.
|
|
Re: Question about inserted OLE objects
llandale - Tue Apr 02 11:41:18 EDT 2013 cliff.sadler - Fri Mar 29 14:23:20 EDT 2013
OK, I'd like to take this a bit further. I have a very large table (many columns wide). We have been maintaining the table in Excel because of ease and familiarity of manipulating columns and rows. This table is stored in DOORS in relation to requirements, and is periodically published to Word.
So, typically, I copy the contents of the Excel sheet into a Word document (11x17 Landscape), save that, and insert it as an OLE into its own object. RPE renders it nicely, and all is good. I would like to be able to see the contents of the table in DOORS, however there seems to be a hard limit on the height and width of an inserted OLE object's "render". Do you know of any way to change the max width, and/or max height of an inserted OLE? It looks like the visible limit is what is shown on a Word Export. Even though the page is wider than the OLE table (not hitting margin issues width wise), it will not render past a certain width, both in the DOORS object, and in the Word exported OLE container in the document.
When I run Kevin's ExpandOLE macro, of course it does come in to the document full width and multi-page height. Perhaps it's just a limitation of OLE.
-
string oleSetHeightandWidth(Attr__,int height,int width,int index)
-
string oleSetMinWidth(Attr__,int width)
-
string oleSetMaxWidth(Attr__,int width)
-
string getOleWidthHeight(EmbeddedOleObject,int&,int&)
The returned string is surely an Error Message, and an "Attr__" looks like o."Object Text".
-Louie
|
|