查看单个帖子
旧 2009-05-07, 03:31 PM   #1
yang686526
高级会员
 
注册日期: 06-11
帖子: 14579
精华: 1
现金: 224494 标准币
资产: 234494 标准币
yang686526 向着好的方向发展
默认 【转帖】searching For Documentation

searching for documentation
searching for documentation
in the sample app, odreadex, there are references to header variables. for example, though not exclusively, lwdispscale. however, there is no mention of lwdispscale or getlwdispscale in the dwgdirect.chm help file.
when i read the header variables using opendwg i get several proxy entity variables, one of which is read using adlwplineenttype (dwg_handle) and returns 883.
when i read all header variable listed in odreadex's dbdumper.cpp nothing corresponds to the 883 which was read from opendwg. in fact none of the proxy entity variables shows up in the header variable list from odreadex.
this is extremely confusing. how do i resolve these discrepancies?
adlwplineenttype() returns the type number used for lightweight polylines in the actual dwg file. the number used for a particular type can vary from file to file, 883 in one file, 511 in another, and so on. this value is not a header variable. dwgdirect replaces this mechanism with the iskindof function, and with the protocol extension mechanism used in odreadex (so clients don't need to deal with the varying type numbers).
header variables functions in dwgdirect are generated by macros, and our documentation generation software does not pick these up. if you look in include/sysvardefs.h the header variables are enumerated, and from these we generate a getxxx() and setxxx() function for each variable, in the oddbdatabase class.
yang686526离线中   回复时引用此帖
GDT自动化论坛(仅游客可见)