Обсуждение: Problem of dialog size.
Hi. I get a strange report from the user who has continued using since 1.4. This cause was that the information left behind to the registry is inheritance... Then, I sent and solved this file. -- pgAdmin_regclean.reg -- Windows Registry Editor Version 5.00 [-HKEY_CURRENT_USER\Software\pgAdmin III] -- It is changed into an initial stage. I find that two or more versions exist more than it. Should we attach a version to a registry key as a plan? Regards, Hiroshi Saito
Hiroshi Saito wrote: > Hi. > > I get a strange report from the user who has continued using since 1.4. > This cause was that the information left behind to the registry is > inheritance... Then, I sent and solved this file. > -- pgAdmin_regclean.reg -- > Windows Registry Editor Version 5.00 > > [-HKEY_CURRENT_USER\Software\pgAdmin III] > -- > It is changed into an initial stage. > > I find that two or more versions exist more than it. > Should we attach a version to a registry key as a plan? No - it's in the archives now if anyone needs it, though I don't recall anyone reporting the issue before. Instead, we should change the dialogue sizing code to ensure they never open too small. I though I had done that, but maybe the user you spoke to has found a new way to invoke the problem? /D
Hi. From: "Dave Page" <dpage@postgresql.org> >> I find that two or more versions exist more than it. >> Should we attach a version to a registry key as a plan? > > No - it's in the archives now if anyone needs it, though I don't recall > anyone reporting the issue before. > > Instead, we should change the dialogue sizing code to ensure they never > open too small. I though I had done that, but maybe the user you spoke > to has found a new way to invoke the problem? Ahh yes,However, This problem reproduces me in the coexistence environment of Ver1.6 and Ver1.8. It seems that, as for it, Ver1.6 is influenced. http://winpg.jp/~saito/pgAdmin/pgadmin_16and18.png Is it recommending so that a new version's may be used? I think that there should just be clear consent. Regards, Hiroshi Saito
Hiroshi Saito wrote: > Hi. > > From: "Dave Page" <dpage@postgresql.org> > >>> I find that two or more versions exist more than it. >>> Should we attach a version to a registry key as a plan? >> >> No - it's in the archives now if anyone needs it, though I don't recall >> anyone reporting the issue before. >> >> Instead, we should change the dialogue sizing code to ensure they never >> open too small. I though I had done that, but maybe the user you spoke >> to has found a new way to invoke the problem? > > Ahh yes,However, This problem reproduces me in the coexistence > environment of Ver1.6 and Ver1.8. It seems that, as for it, Ver1.6 is > influenced. http://winpg.jp/~saito/pgAdmin/pgadmin_16and18.png > Is it recommending so that a new version's may be used? > I think that there should just be clear consent. If you want to use 2 versions side by side, then I guess we need to move many of the settings to somewhere like \Software\pgAdmin III\1.9\xxxx I can do that when I get round to rewriting the settings management code if people want? /D
Hi. From: "Dave Page" <dpage@postgresql.org> > If you want to use 2 versions side by side, then I guess we need to move > many of the settings to somewhere like \Software\pgAdmin III\1.9\xxxx > > I can do that when I get round to rewriting the settings management code > if people want? Probably yes, However, I don't like hypertrophy of a registry.... It seems that but it is not avoided.:-( Regards, Hiroshi Saito