![]() |
2010-06-15
, 21:11
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#2
|
![]() |
2010-06-17
, 15:48
|
Posts: 166 |
Thanked: 106 times |
Joined on Dec 2007
@ Finland
|
#3
|
Isn't the typical wisdom that if you're going to change the backing store, detach it from the display part first, do the change and then re-connect it?
This is what I've seen recommended for GtkTreeViews, for example.
![]() |
2010-06-19
, 10:19
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#4
|
The Following User Says Thank You to nicolai For This Useful Post: | ||
![]() |
2010-06-21
, 08:36
|
Posts: 166 |
Thanked: 106 times |
Joined on Dec 2007
@ Finland
|
#5
|
![]() |
2010-09-13
, 17:41
|
|
Posts: 700 |
Thanked: 846 times |
Joined on Nov 2009
|
#6
|
I had the same problem since PR 1.2
(But I do not have much experience with gtk,
so this may be in fact another problem or just my fault).
I tried to detach the selector from the liststore
by setting the current model to NULL, and then clear the
liststore.
But this gives some warning from the touch selector
(invalid iterator). Finally I got it working by deselecting
any touch selector row. (set selected row to -1).
Maybe this helps
nicolai
Here is a simple example which should demonstrate the behaviour.
Have I understood something wrong? I wouldn't like to use the "changed" callback for the touch selector since it created some problems in my code (not the simple example above).