Hmm. Very interesting that we apparently have the same code but are having different behaviors. Furthermore, I find it odd that the example on pyjs.org/examples is producing a different result depending on whether I am accessing the web page or someone else is. I have tried it in Chrome and Firefox with the same results. As a side note, when I tried it in IE, it wouldn't load and instead threw the following error:
DateField TypeError: Object doesn't support property or method 'addEventListener' I won't be worrying about the above for now, just thought I'd mention it. I will keep looking into it and see if I can get some debug stuff to work. Where do I get this new logging module? On Mon, Apr 2, 2012 at 12:44, lkcl luke <[email protected]> wrote: > On Mon, Apr 2, 2012 at 5:33 PM, David Ripplinger <[email protected]> > wrote: > > I have been investigating this Calendar bug a bit further. So the > calendar > > popup actually comes up offset by one day, but when you click on a > > particular day, it does not copy the apparent date into the date field. > > ok - can i suggest you use either pyjd or the new (yay!) logging > module, start throwing some debug statements in? > > > Instead it copies in the date it should have been if the calendar popup > had > > appeared correctly. It's seems to be holding different information than > what > > is printed on screen, but the confusing thing is that the code appears > to be > > pulling the date directly from the contents of the cell, according to > line > > 283 in Calendar.py: > > > > text = grid.getText(row, col).strip() > > > > Any ideas about how it is possible, with this command, for the two > numbers > > to not match would be helpful. I'll keep looking into it in the mean > time. > > just throw in as many debug statements as you can stand, or install > pyjd and one of the single-stepping (interactive) python debuggers, > i'm sure you'll find one with a google search somewhere. > > hmmm... i just tried compiling the calendar example datefield: i'm > not actually seeing anything wrong, at all. this is with firefox. > you can see a small video captured with xvidcap, here: > > http://pyjs.org/test-0000.mpeg > > l. >
