On 17.11.06 18:00:42, Matt Chambers wrote:
> I actually went ahead and made the changes I needed to move the data into the
> model. Instead of just
> replacing the data entirely, I have a loop for updating and inserting, and
> one
> for deleting. Updating
> existing data works great, adding/re
I actually went ahead and made the changes I needed to move the data
into the model. Instead of just
replacing the data entirely, I have a loop for updating and inserting,
and one for deleting. Updating
existing data works great, adding/removing is where I'm having issues.
My data is based of
Matt Newell wrote:
On Thursday 16 November 2006 13:18, Brent Villalobos wrote:
I'm a PyQt newbie so maybe there's an easier way, but I wrote my own. I
saved out various view attributes, swapped in a new model, and then set the
view to those saved-out variables. It works well and to the end
On Thursday 16 November 2006 13:18, Brent Villalobos wrote:
> I'm a PyQt newbie so maybe there's an easier way, but I wrote my own. I
> saved out various view attributes, swapped in a new model, and then set the
> view to those saved-out variables. It works well and to the end user the
> table ju
I'm a PyQt newbie so maybe there's an easier way, but I wrote my own. I
saved out various view attributes, swapped in a new model, and then set the
view to those saved-out variables. It works well and to the end user the
table just updates without losing any context. It's a little annoying to
As far as I can see there isn't any code that resets the selection
model when the model's reset() method is called. There *is* some funky
behavior with selection models continueing to store indexes that are
no longer valid once the layout of the model changes, though.
On 11/16/06, Matt Chambers <
Is it possible that using one of the View classes, to reset() the model,
but still maintain any selections the users had on items that were in
the old data, and the new data?
Matt
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk
