![]() |
2008-03-19
, 20:10
|
Posts: 35 |
Thanked: 5 times |
Joined on Sep 2007
|
#2
|
![]() |
2008-03-20
, 11:52
|
|
Posts: 283 |
Thanked: 60 times |
Joined on Nov 2005
@ It's dark in here. I hear laughing.
|
#3
|
![]() |
2008-03-20
, 17:30
|
|
Posts: 283 |
Thanked: 60 times |
Joined on Nov 2005
@ It's dark in here. I hear laughing.
|
#4
|
Debugging this thing is incredibly hard. I can't do it in Scratchbox,
because the hildon desktop bindings are not compiled for it. Editing
is then done on the device. I thought this would be OK and that the
cycle of unselecting/code change/selecting the applet would run the new
code changes. But...the system seems to cache the code so that the
unselect/select always invokes the same code. And who knows where
even the simple print or logging statements go...
Does anyone have any suggestions for easier debugging of Python desktop
applets. This is my first project in Python (I know...hard project for
the first time :-) so I'm open to anything.
THanks.