Gareth Jones - Latest Comments in Dojo checkboxes

Re: Dojo checkboxes

Roman — Sat, 07 Mar 2009 04:02:14 -0000

I also ran into a similar issue just now. As I've found out, using dijit.byId is for when you're using dojo widgets. As I wasn't, I had to work on the DOM level, so I used dojo.byId("controlid").checked to see if it was checked.

Re: Dojo checkboxes

garethj — Mon, 03 Nov 2008 11:21:32 -0000

No problem Ryan - thanks for posting anyway :)

Re: Dojo checkboxes

Ryan Littlefield — Wed, 22 Oct 2008 12:19:12 -0000

Opps, didn't notice the other reply. Sorry.

Re: Dojo checkboxes

Ryan Littlefield — Wed, 22 Oct 2008 12:18:38 -0000

Have you tried using dijit.byId instead of dojo.byId?

Re: Dojo checkboxes

garethj — Wed, 27 Aug 2008 13:55:08 -0000

Ah, thanks very much. For anyone interested, I've discovered the reason for this (copied from http://tinyurl.com/58oqey ):

Here's the difference: dijit.byId() returns a Dijit widget instance - technically, an instance of dijit._Widget or one of its subclasses like dijit.Toolbar or dijit.TreeNode.

So here's the way to remember it:

* If you need a DOM Node, use dojo.byId. You need a DOM node anytime you call a standard browser function, change a standard property, etc.
* If you need a widget, use dijit.byId. From it you can access all of the attributes, methods and extension points listed in Part 2.

Useful stuff to know when using digit widgets.

Re: Dojo checkboxes

Gordonk66 — Wed, 27 Aug 2008 12:33:34 -0000

You need to use dijit.byId instead of dojo.byId. Then you're in business without setting a jsId for every widget.