Re: Issues with 1.12.0 (Mac OS X)

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Herouth Maoz <herouth(at)SPAMCOP(dot)NET>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Issues with 1.12.0 (Mac OS X)
Date: 2010-09-25 21:18:54
Message-ID: 4C9E673E.8050801@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Le 25/09/2010 12:20, Herouth Maoz a écrit :
> (I sent this message before but it never came through. I'm guessing the majordomo doesn't accept attachments, so I am sending it without the attachments, and please let me know how I can pass the crash reports to you if you need them).
>
> On 23/09/2010, at 22:42, Guillaume Lelarge wrote:
>>
>>> 2. Column width settings get lost when grid editor is closed (they always have, but this makes losing the window a real PITA).
>>
>> What would you like to have on this issue? we can store the widths of
>> each column on the last query, and we would restore that at the next
>> run, but you could run a completely different query and the new widths
>> could not be appropriate. I'm not sure there is an easy solution to this
>> one.
>
> Well, I'm referring to the grid editor - that is, the tool to "view and edit the current object" (filtered or unfiltered). As far as I know, unless the table schema changed (which I supposed can be checked before display), the grid display will have the same number and order of columns. Or am I overlooking some option there?
>
> Of course, in the free query tool, it's a different story.
>

Well, it's not such a different story. We won't store the customized
sizes of each column for each table you saw. Because it could use a lot
of space on the options file.

We still can do what I explained earlier, ie storing the size of each
column of the table last viewed. And we will restore that, no matter
which table you open. If this could work for you, I can work on this.

>>
>>> 3. Restored connections in browser window cause instability.
>>
>> We would need more to get this "bug" fixed.
>
> OK, I'll try to keep records several times after the computer wakes.
>
> I'm attaching the crash reports from the two crashes that I had so far.
>

Thanks for the two files. Unfortunately, there is nothing in them that
could help me fix this bug.

>>> 4. New icon is not very practical on the Mac.
>>
>> I'll let Dave answer on this one :)
>>
>>> 5. GUI text engine doesn't handle RTL text properly.
>>
>> Seems more a wxWidgets issue to me. And I'm quite sure they'll tell you
>> to use 2.9 instead of 2.8.
>
> Yes, I said I was guessing it's something to do with your GUI engine. Is this something I can actually do or do you mean you have compiled 1.12.0 against an old version of wxWidgets and there's nothing to be done?
>

pgAdmin is compatible with wxWidgets 2.8. 2.9 is mostly a development
release for 3.0, so we didn't actually put a lot of work to be
compatible with 2.9. And there is good chance we won't until 3.0 is out.

--
Guillaume
http://www.postgresql.fr
http://dalibo.com

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2010-09-25 21:21:23 Re: [pgadmin-support] pgAdmin v1.12.0 Released
Previous Message Jason Long 2010-09-25 21:16:13 Re: [pgadmin-support] pgAdmin v1.12.0 Released