POST
|
I've been searching now for a while and can't find an explicit list of the limitations of the component framework exposed to add-in developers (apologies if this is a redundant topic but I just can't seem to find this info). I've found this (from here😞 Most developers will create add-ins if creating a command, tool, combo box, menu or context menu, multi-item, toolbar, tool palette, dockable window, or application extension. However, if multiple interfaces need to be inherited, or if registration is required, an add-in will not work and a custom component needs to be created. For more information, see Building add-ins for ArcGIS Desktop. Can anyone help me understand the multiple interfaces inherited clause? For example, in an extension I have to gain access to the Utility Network Analyst toolbar and get the current network. Is this a case of multiple interfaces being inherited in my extension? From here I found this: for example, you cannot write a custom renderer, a custom workspace, or a custom feature as an add-in. You will need to use the classic COM extensibility approach if your solution includes component types that are unsupported in the add-in framework. Custom workspaces, feature classes, etc. are not supported. Does this mean I can't create a non-spatial Table Feature Class in a user-specified GDB? This coding patterns here are helpful to get started but I have a large standalone extension to migrate from 9.x to 10 and would like to figure out if I could convert it to an add-in. In conclusion, I can't find the 'add-in framework' for reference of the complete list and any help would be great.
... View more
04-01-2012
05:26 PM
|
0
|
0
|
732
|
POST
|
I'm afraid I still can't figure out where to find a comprehensive list of exposed and unexposed ArcObjects for Add-ins. Is there one? I have an existing extension that implements ILayer to retrieve info on the layers in the TOC - is this possible with an Add-in?
... View more
04-01-2012
04:29 PM
|
0
|
0
|
626
|
POST
|
Really useful snippet of code, thanks! I'd like to apply this to a SearchWidget query result. I'm not sure where to begin - where would I insert the modified snippet of code? So far I've only been working with the SearchWidget XML files. Cheers,
... View more
08-12-2011
06:30 AM
|
0
|
0
|
1017
|
POST
|
The saga continues. Editing related tables using ArcSDE/Server versioning, relationship classes, and ArcPad 8 or below is a nightmare, to put it bluntly. I have a number of questions/issues about this process and I'm sure many other people do too. Let me first distill what could be a long rant into a sentence: why has ESRI treated relationships among non-spatial and spatial tables as an afterthought when creating software for distributed database editing? [INDENT]I'm using: ArcGIS Desktop 9.3 ArcPad 8 with ArcPad Studio ArcServer on an Oracle database My database: two spatial feature classes at least 16 related tables. [/INDENT] Here's why I have related tables: because one point can have many surveys - different survey types and/or different survey dates. My hunch is that many more people have a similar database setup than ESRI acknowledges. This quote may sum up the philosophy at ESRI [INDENT] "For most reconcile operations, no conflicts should be encountered. This is because in most organizations, projects and versions represent distinct geographic areas. If you and your coworkers are editing different parts of the map, you shouldn't encounter conflicts." [/INDENT] Sure, but what if two users are editing the same non-spatial table? This does not happen often with versioned and distributed related tables among multiple field data collectors - it happens every time a new feature is created. I hope you great folks out there working on this stuff have encountered a few issues that I have. Here are a couple specific issues I've encountered with ArcPad. [INDENT]1) To check out a feature class using the ArcPad Data Manager toolbar and bring the related tables there needs to be relationship classes created. However, when checking out the actual data (not just the data schema) multiple relationship classes relating two tables will cause much of the data to be left behind. For example, say table A relates 1:M with table B, Table A relates 1:M with table C, and table B also relates 1:M with table C. This is often a rational schema in normalized database design. But, a setup like this will cause much of the data to be left behind upon export. I had to delete the third relationship class in this case. 2) Any tables "parent" to the feature class or "parent" to "child" related tables exported are left behind. For example, if the feature class is called 'SITES' and each SITE is a member of one SYSTEM (the parent table) then 'SYSTEMS' table is left behind when you 'Get data for ArcPad.' Secondly, if a "child" table of SITES, say SURVEY1 has a "parent" table called SURVEY_TYPE then SURVEY_TYPE gets left behind. 3) Just generally, how does the check-in / reconcile process work with related tables when there's a conflict? I am just struggling through this but am I wrong to assume that if there is a conflict between a primary key value in one table and that value is then changed, the changes are only perpetuated to the other related tables if the relatioship class is a 'composite' relationship? Or are these changes synchronized through 'message propagation' in the relationship class? Many thanks in advance for any discussion/help! [/INDENT]
... View more
06-14-2010
06:57 AM
|
0
|
3
|
2405
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|