"too much recursion" error instanciating a dialog derived from "dijit.Dialog"

[guest]

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

[bill]

Please attach a testcase using the "Attach file" button.

[guest]

Derived dialog causes blown stack

[guest]

template DlgTest?.js

[guest]

test to create derived dialog (blows stack)

[guest]

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]…)

[guest]

I'm interested when this is fixed...

[Douglas Hays]

change

dojo.declare("kw.Dialog.DlgTest?", [dijit.Dialog, dijit._Templated],

to

dojo.declare("kw.Dialog.DlgTest?", dijit.Dialog,

[guest]

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]…)

[Douglas Hays]

screen shot of the user's code working

[Douglas Hays]

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

[guest]

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?

[guest]

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.

[Douglas Hays]

User error - subclass DlgTest?.js needed to set templateString:null