Hey Paul,
I thought I'd see what the status of the new wizard was, but got an
error running it:
File "./appWizard.py", line 406, in __init__
dabo.ui.dIcons.getIconBitmap("daboIcon128"))
AttributeError: 'module' object has no attribute 'dIcons'
The script has what I thought was the standard Dabo import for a UI
app:
import dabo.db, dabo.ui, dabo.biz
dabo.ui.loadUI("wx")
So I ran the old wizMaintenanceApp.py to see what I was doing wrong,
and got the following:
[ed@homer demo]$ python wizMaintenanceApp.py
Dabo Info Log: Wed Sep 1 09:44:27 2004: No default UI set.
(DABO_DEFAULT_UI)
UI ERROR: No module named dDataControlMixin
Traceback (most recent call last):
File "wizMaintenanceApp.py", line 863, in ?
wiz = WizMaintenanceApp()
File "wizMaintenanceApp.py", line 405, in __init__
dabo.ui.dIcons.getIconBitmap("daboIcon128"))
AttributeError: 'module' object has no attribute 'dIcons'
I understand the error about the dDataControlMixin, as that is
something you just moved, and somewhere it is still referenced using
the old module pathing. But what's up with the dIcons? What needs to be
changed to get this to work?
___/
/
__/
/
____/
Ed Leafe
On Sep 1, 2004, at 9:47 AM, Ed Leafe wrote:
> I understand the error about the dDataControlMixin, as that is
> something you just moved, and somewhere it is still referenced using
> the old module pathing. But what's up with the dIcons? What needs to
> be changed to get this to work?
As a follow-up, all the controls seem to be broken now:
[ed@homer uiwx]$ python dTextBox.py
Dabo Info Log: Wed Sep 1 09:53:09 2004: No default UI set.
(DABO_DEFAULT_UI)
Traceback (most recent call last):
File "dTextBox.py", line 3, in ?
import dabo.ui.dDataControlMixin as dcm
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/dDataControlMixin.py",
line 5, in ?
import dControlMixin
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/dControlMixin.py", line
8, in ?
class dControlMixin(dabo.ui.dPemMixin):
AttributeError: 'module' object has no attribute 'dPemMixin'
[ed@homer uiwx]$ python dSpinner.py
Dabo Info Log: Wed Sep 1 09:54:00 2004: No default UI set.
(DABO_DEFAULT_UI)
Traceback (most recent call last):
File "dSpinner.py", line 2, in ?
import dabo.ui.dDataControlMixin as dcm
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/dDataControlMixin.py",
line 5, in ?
import dControlMixin
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/dControlMixin.py", line
8, in ?
class dControlMixin(dabo.ui.dPemMixin):
AttributeError: 'module' object has no attribute 'dPemMixin'
[ed@homer uiwx]$
___/
/
__/
/
____/
Ed Leafe
Ed Leafe writes:
> I understand the error about the dDataControlMixin,
> as that is something you just moved, and somewhere it is
> still referenced using the old module pathing. But what's up
> with the dIcons? What needs to be changed to get this to
> work?
Sorry I didn't follow through. I introduced some other problems
with that last commit as well.
Hang on...
--
Paul McNett
Independent Software Consultant
Ed Leafe writes:
> As a follow-up, all the controls seem to be broken
> now:
No, just the tests for the controls. Fixed in the recent commit.
--
Paul McNett
Independent Software Consultant
On Sep 1, 2004, at 11:51 AM, Paul McNett wrote:
>> As a follow-up, all the controls seem to be broken now:
>
> No, just the tests for the controls. Fixed in the recent commit.
Hmm... I ran the update, and then:
[ed@homer uiwx]$ python dTextBox.py
Dabo Info Log: Wed Sep 1 12:23:23 2004: No default UI set.
(DABO_DEFAULT_UI)
Traceback (most recent call last):
File "/usr/local/lib/python2.3/site-packages/dabo/ui/__init__.py",
line 44, in loadUI
exec("from %s import *" % module, globals())
File "<string>", line 1, in ?
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/uiwx/__init__.py", line
27, in ?
from dComboBox import dComboBox
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/uiwx/dComboBox.py",
line 3, in ?
import dEvents
ImportError: No module named dEvents
UI ERROR: No module named dEvents
Dabo Info Log: Wed Sep 1 12:23:23 2004: dEvent Fired:
?.dTextBox.GotFocus
Then if I move the mouse anywhere over the control, I get:
Traceback (most recent call last):
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/uiwx/dPemMixin.py",
line 173, in _onWxMouse
self.raiseEvent(dEvents.MouseEnter, event)
File
"/usr/local/lib/python2.3/site-packages/dabo/ui/uiwx/dPemMixin.py",
line 295, in raiseEvent
dPemMixin.doDefault(eventClass, nativeEvent,
callAfterFunc=wx.CallAfter,
File
"/usr/local/lib/python2.3/site-packages/dabo/common/doDefaultMixin.py",
line 21, in doDefau
return eval('super(cls, self).%s(*args, **kwargs)' % methodName)
File "<string>", line 0, in ?
File
"/usr/local/lib/python2.3/site-packages/dabo/common/eventMixin.py",
line 36, in raiseEvent
event = eventClass(self, uiEvent, *args, **kwargs)
File "/usr/local/lib/python2.3/site-packages/dabo/dEvents.py", line
24, in __init__
self._insertEventData()
File "/usr/local/lib/python2.3/site-packages/dabo/dEvents.py", line
49, in _insertEventData
self._extraLogInfo = "X:%s Y:%s" %
(self.EventData["mousePosition"][0],
KeyError: 'mousePosition'
___/
/
__/
/
____/
Ed Leafe
Ed Leafe writes:
> Hmm... I ran the update, and then:
>
> [ed@homer uiwx]$ python dTextBox.py
> Dabo Info Log: Wed Sep 1 12:23:23 2004: No default UI set.
> (DABO_DEFAULT_UI)
> Traceback (most recent call last):
Ok, just to be sure I didn't have any latent .pyc files hanging around, I did:
[pmcnett@sol dabo]$ cd ..
[pmcnett@sol projects]$ rm -rf dabo
[pmcnett@sol projects]$ svn co svn://paulmcnett.com/dabo/trunk dabo
A dabo/biz
A dabo/biz/test
...[snip]...
Checked out revision 431.
[pmcnett@sol projects]$ cd dabo/ui/uiwx
[pmcnett@sol uiwx]$ python dTextBox.py
Dabo Info Log: Wed Sep 1 10:23:29 2004: No default UI set. (DABO_DEFAULT_UI)
Dabo Info Log: Wed Sep 1 10:23:30 2004: Cannot change the uiType to 'wx', because UI 'wx' is already loaded.
Dabo Info Log: Wed Sep 1 10:23:30 2004: dEvent Fired: ?.dTextBox.GotFocus
...[snip]...
Dabo Info Log: Wed Sep 1 10:23:41 2004: dEvent Fired: ?.dTextBox.Destroy
[pmcnett@sol uiwx]$
I wonder what could be different about our setups? Perhaps you have old .pyc files
that are screwing with you. This can happen because certain .py files were removed
by SVN, but since the .pyc files aren't under version control SVN would have left them.
--
Paul McNett
Independent Software Consultant
Ed Leafe writes:
> from dComboBox import dComboBox
> File
> "/usr/local/lib/python2.3/site-packages/dabo/ui/uiwx/dComboBo
>x.py", line 3, in ?
This part of your error must have to do with local changes on
your end, as the repository's dComboBox.py is empty. Change
your 'import dEvents' line to 'import dabo.dEvents as dEvents'.
--
Paul McNett
Independent Software Consultant
On Sep 1, 2004, at 1:32 PM, Paul McNett wrote:
> This part of your error must have to do with local changes on
> your end, as the repository's dComboBox.py is empty. Change
> your 'import dEvents' line to 'import dabo.dEvents as dEvents'.
Yeah, I recently completed the code for dComboBox as part of my
migration of wxGlade to Dabo. I was going to check it in when I next
worked on the designer.
___/
/
__/
/
____/
Ed Leafe
On Sep 1, 2004, at 1:32 PM, Paul McNett wrote:
>> from dComboBox import dComboBox
>> File
>> "/usr/local/lib/python2.3/site-packages/dabo/ui/uiwx/dComboBo
>> x.py", line 3, in ?
>
> This part of your error must have to do with local changes on
> your end, as the repository's dComboBox.py is empty. Change
> your 'import dEvents' line to 'import dabo.dEvents as dEvents'.
I just figured that out, and was going to let you know what the
problem was when I saw your note. I copied the import statement for
dEvents from other classes, but since it hadn't been checked in, you
couldn't update it to fit with your changes. Now that it's fixed, I'm
able to run the individual classes without problems. Now on to the
wizard!
___/
/
__/
/
____/
Ed Leafe
Ed Leafe writes:
> I just figured that out, and was going to let you
> know what the problem was when I saw your note. I copied the
> import statement for dEvents from other classes, but since it
> hadn't been checked in, you couldn't update it to fit with
> your changes. Now that it's fixed, I'm able to run the
> individual classes without problems. Now on to the wizard!
Thanks for implementing dComboBox. That bugged me every single
time I saw it just sitting there, empty.
--
Paul McNett
Independent Software Consultant