With some trepidation about extending this wearisome thread, I thought that
I would post for the benefit of the record some information about a
solution that I found. It is based on a suggestion made by Kristian
Rietveld in the previous incarnation of this thread (which I quoted when I
resurrected
Gorshkov wrote:
> Lack of patience, and the feeling that I was talking to a brick wall, to
> be perfectly honest. I even posted all the code he needed to implement
> the solution - and given that it was only about 20 or 30 lines total, I
> wouldn't exactly call it overly complicated. The only co
Scott Horowitz wrote:
> On Feb 11, 2008 1:35 PM, Gorshkov <[EMAIL PROTECTED]> wrote:
>> Check my first post to you - it contains ALL the code you need, period.
>> I deal with exactly the same problem you have, for exactly the same
>> reasons you have to.
>>
>> Stop trying to implement a toe pedal,
On Feb 11, 2008 1:35 PM, Gorshkov <[EMAIL PROTECTED]> wrote:
> Check my first post to you - it contains ALL the code you need, period.
> I deal with exactly the same problem you have, for exactly the same
> reasons you have to.
>
> Stop trying to implement a toe pedal, and just use the stick shift.
Jeffrey Barish wrote:
> As I observed previously, there are usually ways to design around
> limitations of toolkits, but sometimes they are awkward. In my case, the
> TreeView in question is instantiated in class A. Class A is instantiated
> in class B. The code that needs to know the column wid
As I observed previously, there are usually ways to design around
limitations of toolkits, but sometimes they are awkward. In my case, the
TreeView in question is instantiated in class A. Class A is instantiated
in class B. The code that needs to know the column widths is in class D
which is ins
Jeffrey Barish wrote:
> Gorshkov wrote:
>
>> You don't have to set the widths again every time you show them. When
>> the TreeView becomes hidden/not hidden or visible/not visible, it will
>> have the same properties and values it had the last time it was visible.
>> The ONLY time you have set tho
Jeffrey Barish wrote:
> Gorshkov wrote:
>
>> You don't have to set the widths again every time you show them. When
>> the TreeView becomes hidden/not hidden or visible/not visible, it will
>> have the same properties and values it had the last time it was visible.
>> The ONLY time you have set tho
Gorshkov wrote:
> You don't have to set the widths again every time you show them. When
> the TreeView becomes hidden/not hidden or visible/not visible, it will
> have the same properties and values it had the last time it was visible.
> The ONLY time you have set those values is when you display/
Jeffrey Barish wrote:
> Gorshkov wrote:
>
>> I do this exact thing in an application I'm developing now. But I only
>> do it in one place - a callback routine that is called for both the
>> delete and destroy events.
>
> Thank you for your suggestions.
>
> I don't get a delete, destroy, or
Gorshkov wrote:
> I do this exact thing in an application I'm developing now. But I only
> do it in one place - a callback routine that is called for both the
> delete and destroy events.
Thank you for your suggestions.
I don't get a delete, destroy, or even a hide signal when the treeview
disap
Jeffrey Barish wrote:
> Kristian Rietveld wrote:
>
> The problem with your first suggestion is that I have to hook every
> situation in which the tree view can be destroyed. The obvious one is when
> I change data sets. Exiting the program is another. There will be others
> when I implement more
Kristian Rietveld wrote:
> If just saving the column widths of the tree view when the tree view is
> destroyed is not enough, the easiest way to do this is probably to
> connect to the "notify::width" signal on each column. Remember to keep
> the callback fast (do not write to files, etc) as your
Kristian Rietveld wrote:
> If just saving the column widths of the tree view when the tree view is
> destroyed is not enough, the easiest way to do this is probably to
> connect to the "notify::width" signal on each column. Remember to keep
> the callback fast (do not write to files, etc) as your
On Tue, Sep 25, 2007 at 05:45:51PM -0600, Jeffrey Barish wrote:
> Is there a way to be notified when the width of a column in a treeview
> changes? I would like to record the new column widths so that I can set
> them to the same values the next time the window opens. The only signal in
> TreeVie
Is there a way to be notified when the width of a column in a treeview
changes? I would like to record the new column widths so that I can set
them to the same values the next time the window opens. The only signal in
TreeViewColumn is clicked, which doesn't seem to do what I need.
--
Jeffrey Ba
16 matches
Mail list logo
