Doug Hall wrote:
>This particular component is Foundation, but unless it's corrupted somehow,
>I don't think that's relevant to my problem. While the component structure
>itself validates with a checkmark in the Maintenance Security Center, the
>structure index doesn't seem to work. I can move my structure index of the
>component to another folder, reopen the component (thus rebuilding the
>index), build the component, placing the built component into my parent
>DB's (components) folder. Yet, when I <command>+K on a component method
>from the parent DB, it will always point me to some local object method
>instead. It used to simply show me that it was a component message, but it
>would at least point me to the right thing.
>Yesterday, I realized that it's not even getting some of my constants
>right. If I do Alert2("Some message";FND_Dlg_NoteIcon), it shows me the
>Fnd_Dlg_WarnIcon icon, instead.
Doug,
Are you using a compiled component, or are you just putting the component
structure in the host’s “Components” folder? You said “… build the component”
so I’d assume compiled, but just making sure.
Either way, you won’t be able to edit the component methods while in the host,
even if you’re using the source structure in the Components folder. You can
trace execution (if not using a compiled component), but you can’t edit or even
view the code.
Regarding the constants, if you’re using the source DB in the host’s Components
folder you’ll need to include the constants file(s) from the component DB in
the host’s “Resources” folder, as well as include the “.4DIndy” file from the
component’s folder in the host’s “Components” folder. If you’re using a
compiled component, you don’t need either of these (and I imagine including
them would cause problems).
Have you checked the host’s Resources folder to make sure you don’t have any
duplicate IDs?
Regards,
Ben Kershaw
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
