wxPython-users archive @ ASPN

Re: [wxPython-users] Associating nodes in a tree with strings

Saketh Bhamidipati (saketh.bhamidipati@...)

On 6/22/06, Josiah Carlson

>
> Robin Dunn  > Josiah Carlson wrote:
> > > Creating your own tree, if wxPython did not offer such functionality
> > > already, would be fairly easy.  The trick is that while you may not
> > > expect tree nodes to share names, other trees that could use such
> > > functionality may expect to share names, so using node names as keys
> in
> > > a dictionary probably isn't the best idea.  You could use tree node
> ids,
> > > as I believe those are unique within the tree.
> >
> > I don't think they are hashable however, which is a requirement of
> > dictionary keys.  I would probably do it simply by generating a unique
> > ID and making that be the dictionary key, and also set it as the tree
> > item data.
>
> The tree node ids are integers, so should be hashable.  Whether or not
> to keep the information in a dictionary or in the tree depends on
> whether or not such uses are desireable or necessary (and whether the
> user wants to traverse the tree to pull the information out).
>
> - Josiah
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-users-unsubscribe@...
> For additional commands, e-mail: wxPython-users-help@...
>
> I found that the hash was completely unnecessary. I am now able to
accomplish the same thing using only the SetPyData and GetPyData methods,
without adding any new data structures.

Re: [wxPython-users] Associating nodes in a tree with strings

Josiah Carlson (jcarlson@...)

Robin Dunn  Josiah Carlson wrote:
> > Creating your own tree, if wxPython did not offer such functionality
> > already, would be fairly easy.  The trick is that while you may not
> > expect tree nodes to share names, other trees that could use such
> > functionality may expect to share names, so using node names as keys in
> > a dictionary probably isn't the best idea.	You could use tree node ids,
> > as I believe those are unique within the tree.
> 
> I don't think they are hashable however, which is a requirement of 
> dictionary keys.  I would probably do it simply by generating a unique 
> ID and making that be the dictionary key, and also set it as the tree 
> item data.

The tree node ids are integers, so should be hashable.	Whether or not
to keep the information in a dictionary or in the tree depends on
whether or not such uses are desireable or necessary (and whether the
user wants to traverse the tree to pull the information out).

 - Josiah


---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...

Re: [wxPython-users] Wizard/panel questions...

A.M. (cuberootva@...)

That was easy enough. I was calling my
sizer's Layout function.

Thank you much!

On 6/22/06, Robin Dunn  A.M. wrote:
>
> > Now then, say I want to reset this page (or panel) to look like it
> > first started. I binded the letter "E" to call the above initWindow
> > again assuming that it would destroy everything and start from
> > scratch. It seems to do just that but the positioning is way off. It
> > resembles something like:
> >
> > es here
> >
> > And that's about it. No line or anything. If I hit the "A" key at this
> > point I can sort of see a VERY small portion (maybe 2px or so) of the
> > TextCtrl being rendered on the left side of the panel. The funny part
> > is I can click Next to move to the next page and then click back to
> > return and everything is rendered fine again! Note: this only happens
> > in Linux...in Windows the positioning is still screwed up. This led me
> > to believe it was a repaint issued but I have tried different
> > combinations of Update, Refresh, Layout, and RecalcSizes.
> >
> > Any thoughts, ideas, suggestions?
>
> Call self.Layout()
>
> --
> Robin Dunn
> Software Craftsman
> http://wxPython.org  Java give you jitters?  Relax with wxPython!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-users-unsubscribe@...
> For additional commands, e-mail: wxPython-users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...

Re: [wxPython-users] Associating nodes in a tree with strings

Robin Dunn (robin@...)

Josiah Carlson wrote:
> "Saketh Bhamidipati" > I am trying to associate nodes in my TreeCtrl with strings. For example, a
>> node "Lion" would have the string "King of the beasts" associated with it.
>> This functionality is not native to TreeCtrl.
> 
> It is native to wxPython TreeCtrls:
>     tree.SetPyData(node, data)
> 
> 
>> (Would it be better if I just created my own class, derived from wx.TreeCtrl?
>> Or would the problem remain equally as difficult?) I tried studying the
>> outlining application Leo's code to understand how it accomplishes the task,
>> but I found no help.
> 
> Creating your own tree, if wxPython did not offer such functionality
> already, would be fairly easy.  The trick is that while you may not
> expect tree nodes to share names, other trees that could use such
> functionality may expect to share names, so using node names as keys in
> a dictionary probably isn't the best idea.  You could use tree node ids,
> as I believe those are unique within the tree.

I don't think they are hashable however, which is a requirement of 
dictionary keys.  I would probably do it simply by generating a unique 
ID and making that be the dictionary key, and also set it as the tree 
item data.

-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!


---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...

Re: [wxPython-users] wxGrid and wxGridEvent Questions

Robin Dunn (robin@...)

Valeriy Pogrebitskiy wrote:
> I suspect my group is not the only one having these problems�?� Please 
> help answer these questions (below) and point to the right code sample�?�
> 
> In the grid (wxGrid), editors (subclasses of wxPyGridCellEditor) "react" 
> only after second click (or tab into the cell, and then click). First 
> click (or tab into the cell) does not do anything to activate the editor 
> - its only function is to "select" a given cell. So cell selection 
> always "eats" initial click (or tab). This may not be such a big deal 
> for a simple text control, but it does make big deal for other types of 
> editors (check box, choice list, combo box) - as these require extra 
> click to perform an action (check/uncheck check box, expand drop-down 
> list, etc), requiring users make at least 2 clicks. This does not happen 
> outside of grid�?�
> 
> So questions are:
> 
> 1.	  Is there any way to "eliminate" extra click by enabling editor 
> control at the same time as cell selection is done?

See wx.lib.mixins.grid.GridAutoEditMixin


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!


---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...

Re: [wxPython-users] Wizard/panel questions...

Robin Dunn (robin@...)

A.M. wrote:

> Now then, say I want to reset this page (or panel) to look like it
> first started. I binded the letter "E" to call the above initWindow
> again assuming that it would destroy everything and start from
> scratch. It seems to do just that but the positioning is way off. It
> resembles something like:
> 
> es here
> 
> And that's about it. No line or anything. If I hit the "A" key at this
> point I can sort of see a VERY small portion (maybe 2px or so) of the
> TextCtrl being rendered on the left side of the panel. The funny part
> is I can click Next to move to the next page and then click back to
> return and everything is rendered fine again! Note: this only happens
> in Linux...in Windows the positioning is still screwed up. This led me
> to believe it was a repaint issued but I have tried different
> combinations of Update, Refresh, Layout, and RecalcSizes.
> 
> Any thoughts, ideas, suggestions?

Call self.Layout()

-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!


---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...

Re: [wxPython-users] wxPython for AMD64 on Windows

Robin Dunn (robin@...)

Hengel, Simon wrote:
> Hello,
> is there any hope for an official AMD64/Windows build of wxPython once
> Python 2.5 final is released?
> 
> Is somebody already experimenting with wxPython and Python 2.5 on
> AMD64/Windows?

Lack of appropriate hardware makes this a little difficult for me.  ;-)

> How difficult will it be to do a custom build?

Not hard if you have the tools needed.	See http://wxpython.org/builddoc.php


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!


---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...

[wxPython-users] wxGrid and wxGridEvent Questions

Valeriy Pogrebitskiy (vpogrebitskiy@...)

I suspect my group is not the only one
having these problems... Please
help answer these questions (below) and point to the right code
sample...

In the grid (wxGrid), editors (subclasses of wxPyGridCellEditor) "react"
only after second click (or tab into the cell, and then click). First
click (or tab into the cell) does not do anything to activate the editor
- its only function is to "select" a given cell. So cell selection
always "eats" initial click (or tab). This may not be such a big deal
for a simple text control, but it does make big deal for other types of
editors (check box, choice list, combo box) - as these require extra
click to perform an action (check/uncheck check box, expand drop-down
list, etc), requiring users make at least 2 clicks. This does not happen
outside of grid...

So questions are:
1.	Is there any way to "eliminate" extra click by enabling editor
control at the same time as cell selection is done?
2.	If (1) is not possible - how can second click (or double-click)
event (EVT_GRID_CELL_LEFT_CLICK, EVT_GRID_CELL_LEFT_DCLICK) be "forced"
in code? I tried creating single-click event handler that generates
double-click event in turn, but that does not activate the editor


Valeriy Pogrebitskiy
Fund Development Services
Work: (212) 920-3547
Email: vpogrebi@...

[wxPython-users] PyAUI bug maybe

Dj Gilcrease (digitalxero@...)

I am experiencing an oddity while
using PyAUI 0.9.2 development
version. I have a window which is not being managed by PyAUI that has
some static text, a checklistbox and some buttons. If I call it after
I have called self._mgr.LoadPerspective(layout) then only the static
text is rendered. If I comment out the call to load perspective then
the window renders as expected. I have attached a simple demo. If you
comment out line 76 you will see that the dialog renders properly

[wxPython-users] wxPython for AMD64 on Windows

Simon Hengel (simon.hengel@...)

Hello,
is there any hope for an official AMD64/Windows build of wxPython once
Python 2.5 final is released?

Is somebody already experimenting with wxPython and Python 2.5 on
AMD64/Windows? How difficult will it be to do a custom build?

Cheers, Simon.

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@...
For additional commands, e-mail: wxPython-users-help@...