fail to define new view type on libmgr

Update: I was able to solve 50% of the issue - now once a gds lib  exist, and inside it there is a view in the right pattern : block.gds - virtuoso uses the app "run_ic_workB"  - and the layout open successfully.

             I guess this mean that all 3 triggers were registered correctly. now i still left with the issue that , on library manager , i still dont see under  View type ( when creating a new cell view) the required "block" type

here is the new code:

DataFormat GDSII {
Pattern=block.gds;
Preferred_Editor=run_ic_workB;
dfII_ViewType=block;
Co_Managed = block.gds master.tag prop.xx;
}

ViewAlias {

block=GDSII;

}

Tool GDSII {}

i know that the data.reg is being red because I deliberate syntax error it  and make sure virtuoso complain.

thx

meny

Actually the lines from the first post showed 'gdsLay' in the 'Type' selection field in LibraryManager when I tried it, so there might be some other reasons that it did not work on your side.

However, on the second post: the data.reg has dfII_ViewType=block; while the deRegApp on the first has ?viewType "gdsLay"; Although it is unclear if you also modified the deRegApp, these two entries should be same.

Also on the elements of the string for viewNameToTypeList: first is the viewname and second is the corresponding viewtype, so "gdsLay gds" would put "gdsLay" to the viewname field when viewtype "gds" is selected; but your actual naming suggests the opposit.

thx for the response . here is the final code , that is still 50% operational:

// Data Register file for adding netscape and pdf views
// Date: 08/21/2013

DataFormat Netscape {
Pattern = netscape_url.htm;
Default_Editor = Netscape;
dfII_ViewType = netscape_url;
Co_Managed = netscape_url.htm master.tag prop.xx;
}

DataFormat Gdsii {
Pattern=block.gds;
Preferred_Editor=run_ic_workB;
dfII_ViewType=block;
Co_Managed= block.gds master.tag;
}

DataFormat Acroread {
Pattern=document.pdf;
Preferred_Editor=Acroread L;
dfII_ViewType=document;
Co_Managed=document.pdf master.tag ;
}

ViewAlias {
netscape_url=Netscape;
document=Acroread;
block=Gdsii;

}

Tool Netscape {}
Tool Acroread {}
Tool Gdsii {}

envSetVal("graphic" "viewNameToTypeList" 'string "pdf pdf, pdf document, OOo document.od, document document.od*, block block.gds")

the string "block" dont appear at the  cell view type field, while all the others do. 

i dont publish the triggers because these are seems to load fine , and the required action of launching the wrapper "run_ic_workB"  works. 

try this:

DataFormat Netscape {
Pattern = netscape_url.htm;
Default_Editor = Netscape;
dfII_ViewType = netscape_url;
Co_Managed = netscape_url.htm master.tag prop.xx;
}

DataFormat run_ic_workB {
Pattern=block.gds;
Preferred_Editor=run_ic_workB;
dfII_ViewType=block;
Co_Managed= block.gds master.tag;
}


DataFormat Acroread {
Pattern=document.pdf;
Preferred_Editor=Acroread L;
dfII_ViewType=document;
Co_Managed=document.pdf master.tag ;
}

ViewAlias {
netscape_url=Netscape;
document=Acroread;
block=run_ic_workB;

}

Tool Netscape {}
Tool Acroread {}
Tool run_ic_workB {}

If you use the original SKILL code from the first post (which had ?viewType "gdsLay"), and this in the data.reg, it should work:

DataFormat Run_ic_workB {
Pattern = block.gds;
Default_Editor = Run_ic_workB;
dfII_ViewType = gdsLay;
Co_Managed = block.gds master.tag prop.xx;
}

ViewAlias {
gdsLay=Run_ic_workB;

}

Tool Run_ic_workB {}

The Default_Editor needs to have a corresponding Tool name in the data.reg. The dfII_ViewType needs to match the ?viewType in the deRegApp. That's about it...

I agree though - this is not very obvious and easy to get wrong, with little feedback when it's wrong (it simply doesn't work).

Andrew.