Ok, I've reproduced it. It's only with Ext::Dialog and only with boost without thread-support (and I'm not able to enable threads, I don't know why). On my test-pc the threads are enabled and there it is ok.
Greetings Torsten Koen Deforche schrieb: > Hey Torsten, > > 2008/12/18 Torsten Schulz <[email protected]>: > >> Hello, >> >> what means following error: >> Wt internal error: TypeError: Wt2_2_1.getElement("elo2ec") is null, >> code: undefined, description: undefined? >> > > It means that something caused the server-side widget tree and > client-side DOM tree to get out of sync, and this would indicate > almost certainly a bug in the library. > > If you can reproduce it, we would appreciate some more explanation, > and possibly a test case. > > >> And how can I find it? >> > > What I usually do is remove the exception catching code in > src/web/skeleton/Wt.js, from where this error message is displayed. > Then, you can find out the code that causes the exception using a > JavaScript debugger. > > Regards, > koen > > ------------------------------------------------------------------------------ > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > > ------------------------------------------------------------------------------ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
