Kbase 19091: Why Error 4044 Happens (Invalid UIC Method Called)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/09/1999 |
|
Why Error 4044 Happens (Invalid UIC Method Called)
Title: Why Error 4044 Happens (Invalid UIC Method Called)
KnowledgeBase Number: 19091
Creation Date: 02-SEP-99
Modified Date:
This document applies to: Progress 7.3 and higher
Version and Release Number: 9.0B
Summary:
Customers often wonder what can cause the following error:
UIM Error: Invalid UIC method called. (4044)
This is an internal error which tells us that Progress tried to do
something that we haven't programmed it to do. It occurs when
Progress calls a function which doesn't exist for a particular
widget. For example, it would happen if we tried to call a method
or set an attribute for the status bar. The status bar doesn't have
any attributes or methods so Progress would display this error. It
indicates that we did something wrong internally. There is no harm
done unless it crashes after displaying the message.
This error can happen if the application makes heavy use of creating
and destroying widget or procedure handles. A handle is essentially
a direct memory pointer. We have protection ensuring that a stale
widget handle cannot be referenced after it has been free'd from
memory. However, there is a rare case that can happen where a handle
can point to an internal widghet structure which has actually been
destroyed and another widget of a different type has been reallocated
and given the same memory address. There are "internal" widget types
which have the same UIC structure yet do not have the same basic
methods. The status line is one of those widgets.