Opened 14 years ago
Closed 13 years ago
#4704 closed defect (invalid)
"too much recursion" error instanciating a dialog derived from "dijit.Dialog"
Reported by: | guest | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Dijit | Version: | 0.9 |
Keywords: | Cc: | [email protected]… | |
Blocked By: | Blocking: |
Description
I've been defining some new dialogs derived from dijit.Dialog using .9 release. I updated to the 10/10 nightly build to see how the grid integration was going. I now get "too much recursion" errors trying to instanciate my derived dialogs. Seems like _findMethod() is blowing the stack.
email: dave at photomann.com
Attachments (4)
Change History (13)
comment:1 Changed 14 years ago by
Component: | General → Dijit |
---|---|
Owner: | anonymous deleted |
comment:2 Changed 13 years ago by
I've added an example that causes the blown stack. This seems to effect any of our derived widgets (not just dialogs). There must be something basic I'm doing wrong. Thanks, Dave ([email protected]…)
comment:4 Changed 13 years ago by
Cc: | [email protected]… added |
---|---|
Resolution: | → invalid |
Status: | new → closed |
comment:5 Changed 13 years ago by
Resolution: | invalid |
---|---|
Status: | closed → reopened |
I've already tried this, but if you don't mixin dijit._Templated, my derived dialog template isn't used. ie. I get an empty dialog as it's using the template from dijit.Dialog.
How should I specify the derived object's template? The following has no effect in the derived object: templatePath: dojo.moduleUrl("kw.Dialog","templates/DlgTest.html"),
Thanks for your time, -Dave ([email protected]…)
comment:6 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
This continues to appear to be a user error.
I'm using the latest trunk build, and created the kw
directory structure as a sibling to dojo and dijit.
dojo/
dijit/
kw/
Dialog/
templates/
junk.html
comment:7 Changed 13 years ago by
Resolution: | invalid |
---|---|
Status: | closed → reopened |
I'm sorry to be a pain, but this only works if you modify Dialog.js and set the templateString to null. If Dialog has a templateString (as dijit core does), the derived class's templatePath is not used. I just updated to the 10/24 nightly build and get an empty dialog. Does your dialog.js not have a templateString?
comment:8 Changed 13 years ago by
I think I figured it out. I guess if you set templateString in the derived object to null, then the templatePath will be used. If you don't explicitly add templateString:null, to the derived class, it doesn't work. Still not sure why it would work for you unless your Dialog.js templateString is null.
Thanks for the help... I guess you can close this now.
comment:9 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
User error - subclass DlgTest?.js needed to set templateString:null
Please attach a testcase using the "Attach file" button.