Обсуждение: pgadmin3 osx - two issues

Поиск
Список
Период
Сортировка

pgadmin3 osx - two issues

От
"Otto Bretz"
Дата:
Hi there,

thanks for a very useful application. I'm running 1.8b5 on OSX and I
have to small annoyances.

1. If I want to change some settings for a table, I navigate to the
table in the left pane and then rightclick the table in the top-right
list and select properies. Then the application starts selecting more
tables by itself. See attached screenshot [1]. This happens with all
rightclick actions.

2. I usually tunnel the connection to the server via ssh and if that
connection goes down (same thing happens if I kill the ssh process)
while I work with something else, when I return to pgadmin and try to
do something the app dies and the window dissapears, not even a
crashreport is created.

[1] http://bayimg.com/AAhPiAABb

cheers,
Otto


Re: pgadmin3 osx - two issues

От
Dave Page
Дата:
Otto Bretz wrote:
> Hi there,
> 
> thanks for a very useful application. I'm running 1.8b5 on OSX and I
> have to small annoyances.
> 
> 1. If I want to change some settings for a table, I navigate to the
> table in the left pane and then rightclick the table in the top-right
> list and select properies. Then the application starts selecting more
> tables by itself. See attached screenshot [1]. This happens with all
> rightclick actions.

That's really odd - and seems quite Mac specific. I have no idea what's
causing it unfortunately - it seems to fall into the category of
'bizarre quirk'. I also notice that the resulting property dialogue ends
up in the background.

I'll put some more time into this, but just in case you didn't realise -
you can double-click the objects in the list to open their properties
dialogues. That works just fine.

> 2. I usually tunnel the connection to the server via ssh and if that
> connection goes down (same thing happens if I kill the ssh process)
> while I work with something else, when I return to pgadmin and try to
> do something the app dies and the window dissapears, not even a
> crashreport is created.

This seems to be a Mac-specific bug in the tree refresh code. It's
getting upset when it tries to update the node that's being refreshed. I
added a shortcut to ceck the connection and abort the refresh a little
earlier which seems to solve it.

Thanks, Dave.