On Dec 20, 2007, at 7:12 AM, Dennis Meulensteen wrote:
> I have been dabbling in Dabo for about a week now and I have
> noticed that the
> ClassDesigner won't start the first time...
>
> ps -Al reveals that python is running, but has no child processes.
> The console
> shows about 100 errors, but those are just the usual warnings:
> (python:4382): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion
> `GTK_IS_WIDGET (widget)' failed
> and
> (python:4534): Gtk-WARNING **: gtkwidget.c:4249: no accelerator
> (113,4)
> installed in accel group (0x2853b80) for GtkImageMenuItem (0x2700a10)
>
> When I run it a second or third time and so on, it throws about 400
> errors and
> starts up just fine. Python still running (of course).
Are you starting it by running 'python ClassDesigner.py' from the
'ide' directory? I see those spurious Gtk warnings, but never have I
seen it fail to launch.
> The only other "oddness" I've noticed is that the Class Designer is
> slow as
> molasses, somewhat slower than the famous screencasts. Anyone have
> any tips
> for speeding it up?!? I have a very recent dual core system with no
> swapping
> going on at all. Both cores are being used by python as far as I
> can see
> (total CPU utilization up to around 85%).
This combined with your previous comment suggests that you have
something else interfering with the process. If you run 'top', do you
see any processes that are taking up CPU cycles?
> One more thing I've noticed is I can no longer run an app from the
> designer
> after certain types of errors (not all) it gives me no errors when
> I select
> Run from the menu but won't run the app either without me first
> quitting the
> ClassDesigner and then restarting it. If anyone (Ed?) is interested
> in more
> info I'll gladly help out.
The "running" takes place in the same process as the Class Designer,
so if you encounter an error, it can prevent the code from running
again. BTW, I'm always interested in squashing any bugs you run into,
so please post any and all tracebacks.
> None of this is really critical to me, it's just that I thought
> some of you
> Dabo Devs would like to know about stuff like this.
The problem with developing something like this is that it will run
great on our systems, so we release it. But until others report the
problems they are finding on their systems, it will never improve to
the level it needs to be. So please, keep the reports coming!
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
