Bug #216
closed[ WCalendar and Wt::Ext::Calendar ] j103 is null, code: undefined, description: undefined
0%
Description
After clicking on Calendar widgets ( Both Wt:: and Ext:: versions ) couple of times
I get this error:
Wt internal error: TypeError: j103 is null, code: undefined, description: undefined
I would submit the whole project, but unfortunately , it is quite big :)
Regs,
Dushan Savich
dushansavich@yahoo.com
Files
Updated by Koen Deforche over 14 years ago
- Status changed from New to InProgress
- Assignee set to Pieter Libin
Dushan,
any more suggestions on where to look?
Do you get it on all browsers or only specific ones?
If possible, can you get a JavaScript stacktrace when setting debugging of true in wt_config.xml ?
Thanks,
koen
Updated by Koen Deforche over 14 years ago
- Assignee changed from Pieter Libin to Koen Deforche
Updated by Dushan Savich over 14 years ago
- File output.txt output.txt added
dule@dule-desktop:~/stylet/projects/webace/current/Debug$ ./webace ---http-address=0.0.0.0 ---http-port=8080 ---docroot=. > output.txt
and I've set
true
The stack trace is in the output.txt file.
The server OS: is Ubuntu ( Some animal ) 9.04 .
Client OS: Ubuntu
Browsers: Firefox 3.5.3 , Opera 10., Konqueror and IE6
Boost version is 1.37 and the Wt is the current one found on SourceForge
Btw, this bug doesn't seem to appear on Windows XP under any browser.
Updated by Dushan Savich over 14 years ago
It seems that it is not a Calendar bug after all ..
It's all about what Calendar triggers ...
I've narrowed it down to a WBoxLayout full of images which are repopulated whenever the date changes ...
This is the line which triggers the bug :
*delete* wvBoxLayout_;
wvBoxLayout_ = *new* Wt::WVBoxLayout();
_ ///... add images for the date ... ///_
//My intention was to clear all images along with boxLayout, in order to
Updated by Dushan Savich over 14 years ago
My intention was to clear all images along with boxLayout, in order to in order not to be bothered with removing child images manually ..
I've noticed that similar thing happens when I delete Ext::TabWiget in the same event
Updated by Koen Deforche over 14 years ago
Dushan Savich wrote:
My intention was to clear all images along with boxLayout, in order to in order not to be bothered with removing child images manually ..
I've noticed that similar thing happens when I delete Ext::TabWiget in the same event
Okay, I've found the following in the code:
// FIXME: we do not support deleting the layout_ without deleting all
// children _FIRST_, since deleting the layout automatically removes the
// children too in the DOM.
The workaround is to use WContainerWidget::clear() which first deletes all children, and then calls clear.
This FIXME requires a FIX or at least a big fat warning in the documentation...
Thanks for chasing this down!
Updated by Koen Deforche over 14 years ago
- Status changed from InProgress to Resolved
Now you can delete a layout, and replace it with another layout.
Updated by Koen Deforche about 14 years ago
- Status changed from Resolved to Closed