Re: extending functionality strategy

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Gevik Babakhani" <pgdev(at)xs4all(dot)nl>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: extending functionality strategy
Date: 2008-10-20 08:47:11
Message-ID: 937d27e10810200147j22866a1v8ec17c6941d19962@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Sat, Oct 18, 2008 at 10:43 PM, Gevik Babakhani <pgdev(at)xs4all(dot)nl> wrote:
>> I think the first thing to do is a quick inventory of the
>> lists where we might need to do this.
>
> This is of course needed to be done in order to continue with an item
> ordering/arranging solution. But before we continue we should know that most
> of the lists we use in PGAdmin are of wxListView type (wxListCtrl) which
> have no built-in way to set the item ordering (item index). This leaves us
> with a hacky solution which involves using ItemData from wxListItem. This
> means that item ordering/arranging cannot be done when one of our
> wxListViews uses wxListItem::ItemData. Any thoughts?

Well the other way is to remove the item to be moved, and re-insert it
with a new index.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-10-20 09:25:29 Hot Standby utility and administrator functions
Previous Message Guillaume Lelarge 2008-10-19 21:33:21 Re: Buglets in dlgFunction