|
I’ve made a customized script editor and want to put it in a new relational view. The relational view has two panes top and bottom, the top one has my script editor and what I would like to put in the bottom pane is the history window (like the one in the tool dev. env. layout).
The regular relational view editor doesn’t allow me access to that. Infact even if we edit the tool development environment layout, we can’t put the history window in a pane of our choice.
I thought one way could be to attach the regular script editor in the bottom pane and hide all but the history window section. It appears that there is a large variety of views when editing layouts but the choice is quite limited when editing a custom relational view.
If I can’t get access to the history window in a custom relational view. Is there any other way to capture/access whatever XSI outputs to the history window?
Thanks.
|
|
|
|
Edit the .xsivw view by hand (in a text editor) and try adding a Script History frame.
For example, here is an example view from the XSI SDK workgroup:
<?xml version="1.0" encoding="iso-8859-1"?>
<xsi_file type="RelationalView" xsi_version="4.0.2003.1022" syntax_version="1.0">
<relationalview clsid="{67D87B29-11E9-4F3D-9E5A-5EC0234A1509}" name="RV - Script Editor Dual-Pane" height="540" width="1028">
<definition maxinstances="10000" acceptfocus="true" private="false" defaultsize="100,100,500,500" cmdmap="{00000000-0000-0000-0000-000000000000}" supportedtypes="6" category="SDK Samples"> </definition>
<relations>
</relations>
<frameset orientation="vertical" name="Frameset1" buttonsize="80,30" splitter="movable" sizechild="*,200">
<frameset orientation="horizontal" name="Frameset2" buttonsize="80,30" splitter="movable" sizechild="50%,*">
<frame name="file1" type="Text Editor" primary="false" toolbar="own"> </frame>
<frame name="file2" type="Text Editor" primary="false" toolbar="own"> </frame>
</frameset>
<frame name="log" type="Script History" primary="false" toolbar="none"> </frame>
</frameset>
</relationalview>
</xsi_file>
|
|
|
|
Thanks again Stephen,
I looked through the xsi and sdk docs, it never occured to me to look at the SDK workgroup (which I have been looking at to see how plug-ins work)
|
|
|
