I'm changing the debug messageLevel used in a large application from
WARNING to ALL [0] to complete a port from wafflecone to the
pagan-deities branch of OLS.
One of the INFO messages that shows up is a message about global `menu`
already being defined.
I grepped through the code (I didn't write all of it) and it is not
obvious what LZX (or ECMAScript) is triggering this warning.
What's the best way to track this down? I filed LPP-5545 to track this
issue.
Thanks,
-e
[0]
I'm removing this -
Debug.messageLevel='WARNING';
[0]
INFO: The global `menu` is already defined. To dynamically create a
<menu> element, you will have to use `lz.menu`.
INFO @../../applib/contacts/contacts.lzx#384: getNodeAttribute: p is
null in LzDatapointer
lzx> Debug.inspect(«LzInfo| INFO: The global `menu` is alrea...»)
«LzInfo#1| INFO: The global `menu` is already defined. To dynamically
create a <menu> element, you will have to use `lz.menu`.» {
backtrace: $lzsc$initialize <- lz.class <- makeChild <- makeSomeViews <-
checkQ <- ...
file: null
line: null
message: 'The global `menu` is already defined. To dynamically create a
<menu> element, you will have to use `lz.menu`.'
}«LzInfo#1| INFO: The global `menu` is already defined. To dynamically
create a <menu> element, you will have to use `lz.menu`.»
lzx>
