On Feb 14, 2009, at 6:15 AM, Ricardo Aráoz wrote:
> Hadn't seen them in the api page, but I guessed there might be. Could
> you send me a little code instantiating one of them?
They are typically used in the wrapped methods of the dabo.ui module:
getDirectory() and getFile(). They are documented at
http://dabodev.com/wiki/DaboUiFunctions
Simple example: changing the current directory:
newdir = dabo.ui.getDirectory()
if newdir:
os.chdir(newdir)
> Is dabo wrapping wx.CallAfter()? Where?
dabo.ui.callAfter(). There are other variations, all documented on
the same page noted above:
• dabo.ui.callAfter()
• dabo.ui.callAfterInterval()
• dabo.ui.setAfter()
• dabo.ui.setAfterInterval()
> If I can detect if wx is running it's event loop then I'm in business,
> and the dGrid() (?) would make it easy to implement the browse(cursor)
You mean like dabo.ui.browse()?
I'm sensing a desire to work in wx as if you were doing low-level Fox
stuff. While you can learn a lot about wx in the process, it is likely
that you're re-inventing stuff that we've already done. And you will
never be as productive in Python if you are thinking about it in Fox
terms. It's like me speaking Spanish: since I can only think in
English, I have to do a slow, inefficient (and usually inaccurate)
translation, and the result is never very good. They only way I could
ever learn Spanish is to live somewhere where that was my only option,
and speak it instead of English all the time.
-- Ed Leafe
_______________________________________________
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/[email protected]
