jgfoster wrote:The runtime packager contains a step that identifies warnings and errors. This list typically contains thousands of lines, almost all of which are related to problems in the base image (or vendor-supplied add-ons such as WindowBuilderPro). This makes the tool essentially useless as a way to find actual problems in an application. Does anyone find this tool useful, and if so, how do you deal with the overwhelming number of pre-existing problems?
To make matters worse, if there are unmanaged globals or pool dictionaries, then the display gets a walkback when trying to display the list. Since each the list is redisplayed each time the window is brought to the front (taking several seconds), a new walkback is reported. This makes the window essentially useless since it is impossible to go to the next step.
After spending several hours digging through the various unmanaged things, I've worked it down to two: (1) SampleNLSPoolDictionary (which seems to come from WbNLSExample), and (2) AbtFeatureLoadGrp (I don't know where it comes from). Can we agree that SampleNLSPoolDictionary should be defined with a _PRAGMA_ method? Any idea of the source for AbtFeatureLoadGrp?
Users browsing this forum: Yahoo [Bot] and 1 guest