Re: [pgadmin-hackers] New wx patch
Hiroshi Saito wrote: Hi Andreas. setup0.h isn't contained though "wx-20031026.patch" of the accumulation. you think that it was particularly excluded. Write it in readme-patches.txt. Hm, should be still in it, since -2. Because I was stupid, I did Make-Test again.:-( Does the thing which contains it become wxWindows-pgAdmin3-20031010-6.tar.bz2? Yes, probably, as soon as Dave finds the time to do so. And ID of the doubt?(828538->828537) Typo, corrected. Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] New wx patch
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 27 October 2003 10:32 > To: Hiroshi Saito > Cc: Dave Page; pgadmin-hackers > Subject: Re: [pgadmin-hackers] New wx patch > > > Yes, probably, as soon as Dave finds the time to do so. Go live has been surprisingly quiet so far so I can only assume all our staff are on holiday. I'm building the new snapshot now - this will be based on the 20031026 wx snapshot if all works. Regards, Dave. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] New wx patch
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 27 October 2003 10:32 To: Hiroshi Saito Cc: Dave Page; pgadmin-hackers Subject: Re: [pgadmin-hackers] New wx patch Yes, probably, as soon as Dave finds the time to do so. Go live has been surprisingly quiet so far so I can only assume all our staff are on holiday. I'm building the new snapshot now - this will be based on the 20031026 wx snapshot if all works. Do you mean a wx cvs snapshot as of Oct. 26th? This isn't tested! The name of the new patch file might be misleading, but it is still based on the Oct. 10th wx cvs. Regards, Andreas ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] New wx patch
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 27 October 2003 11:16 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] New wx patch > > Do you mean a wx cvs snapshot as of Oct. 26th? This isn't tested! > The name of the new patch file might be misleading, Combined with your comment of: 'Just get a fresh copy from wx cvs' which at first glance said 'upgrade' to me. > but it is > still based on the Oct. 10th wx cvs. Probably a good thing because 20031026 doesn't work. It just hangs without even showing the splash screen. Regards, Dave. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] New wx patch
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 27 October 2003 11:16 To: Dave Page Cc: pgadmin-hackers Subject: Re: [pgadmin-hackers] New wx patch Do you mean a wx cvs snapshot as of Oct. 26th? This isn't tested! The name of the new patch file might be misleading, Combined with your comment of: 'Just get a fresh copy from wx cvs' which at first glance said 'upgrade' to me. Sorry to be too unprecise. I meant 'get a fresh copy of that 3 files with the sticky option 20031010'. Probably a good thing because 20031026 doesn't work. I'm not too surprised... As long as there's not a real good reason (major platform enhancement, release) there's no reason to try cvs head. All new wx controls we need are contained in the pgAdmin3 sources. Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] New wx patch
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 27 October 2003 12:04 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] New wx patch > > Dave Page wrote: > > > > >Probably a good thing because 20031026 doesn't work. > > > > I'm not too surprised... > As long as there's not a real good reason (major platform > enhancement, > release) there's no reason to try cvs head. All new wx > controls we need > are contained in the pgAdmin3 sources. Although I now find that 20031010 hangs in the same way :-( No logfile is created. Regards, Dave. [EMAIL PROTECTED]:/usr/local/src/pgadmin3# gdb src/pgadmin3 GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-slackware-linux"... (gdb) run Starting program: /usr/local/src/pgadmin3/src/pgadmin3 [New Thread 16384 (LWP 14288)] Program received signal SIGINT, Interrupt. [Switching to Thread 16384 (LWP 14288)] 0x40795d61 in sigsuspend () from /lib/libc.so.6 Current language: auto; currently c (gdb) bt #0 0x40795d61 in sigsuspend () from /lib/libc.so.6 #1 0x40722128 in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #2 0x407243cc in __pthread_alt_lock () from /lib/libpthread.so.0 #3 0x40720490 in pthread_mutex_lock () from /lib/libpthread.so.0 #4 0x085db7c5 in wxMutexInternal::Lock() (this=0x88c4280) at src/unix/threadpsx.cpp:244 #5 0x085de6de in wxMutex::Lock() (this=0x88bff80) at include/wx/thrimpl.cpp:44 #6 0x085df145 in wxCriticalSection::Enter() (this=0x88bff80) at include/wx/thread.h:270 #7 0x085df19b in wxCriticalSectionLocker (this=0xb1c0, [EMAIL PROTECTED]) at include/wx/thread.h:285 #8 0x085ad873 in wxVLogError(wchar_t const*, char*) (szFormat=0x87430c0, argptr=0xb204 "ôÆ\216\b(òÿ¿v\030~@") at src/common/log.cpp:167 #9 0x085ad8fc in wxLogError(wchar_t const*, ...) (szFormat=0x87430c0) at src/common/log.cpp:167 #10 0x085ba1f0 in wxCSConv::DoCreate() const (this=0x88c2038) at src/common/strconv.cpp:1420 #11 0x085ba297 in wxCSConv::CreateConvIfNeeded() const (this=0x88c2038) at src/common/strconv.cpp:1448 #12 0x085ba34f in wxCSConv::WC2MB(char*, wchar_t const*, unsigned) const ( this=0x88c2038, buf=0x0, psz=0x8740998, n=0) at src/common/strconv.cpp:1474 #13 0x085b8433 in wxMBConv::cWC2MB(wchar_t const*) const (this=0x88c2038, pwz=0x8740998) at src/common/strconv.cpp:187 #14 0x085baab5 in wxMBConv::cWX2MB(wchar_t const*) const (this=0x88c2038, psz=0x8740998) at include/wx/strconv.h:56 #15 0x085cc971 in wxStrftime(wchar_t*, unsigned, wchar_t const*, tm const*) ( s=0xb400, max=256, fmt=0x8740998, tm=0x4089e920) at src/common/wxchar.cpp:1312 #16 0x085ae5a2 in wxLog::TimeStamp(wxString*) (str=0xb840) at src/common/log.cpp:456 #17 0x085aea8c in wxLogStderr::DoLogString(wchar_t const*, long) ( this=0x88d8078, szString=0x88ebf44) at src/common/log.cpp:542 #18 0x085ae759 in wxLog::DoLog(unsigned long, wchar_t const*, long) ( this=0x88d8078, level=1, szString=0x88bbf80, t=1067258475) at src/common/log.cpp:478 #19 0x085af2d3 in wxLog::OnLog(unsigned long, wchar_t const*, long) (level=1, szString=0x88bbf80, t=1067258475) at include/wx/log.h:141 #20 0x085ad8a5 in wxVLogError(wchar_t const*, char*) (szFormat=0x87430c0, argptr=0xb944 "¤Ï\216\bhùÿ¿v\030~@") at src/common/log.cpp:167 #21 0x085ad8fc in wxLogError(wchar_t const*, ...) (szFormat=0x87430c0) at src/common/log.cpp:167 #22 0x085ba1f0 in wxCSConv::DoCreate() const (this=0x88c2038) at src/common/strconv.cpp:1420 #23 0x085ba297 in wxCSConv::CreateConvIfNeeded() const (this=0x88c2038) at src/common/strconv.cpp:1448 #24 0x085ba2bb in wxCSConv::MB2WC(wchar_t*, char const*, unsigned) const ( this=0x88c2038, buf=0x0, psz=0xbcb7 "/usr/local/src/pgadmin3/src/pgadmin3", n=0) at src/common/strconv.cpp:1455 #25 0x085b8316 in wxMBConv::cMB2WC(char const*) const (this=0x88c2038, psz=0xbcb7 "/usr/local/src/pgadmin3/src/pgadmin3") at src/common/strconv.cpp:167 #26 0x085baa8f in wxMBConv::cMB2WX(char const*) const (this=0x88c2038, psz=0xbcb7 "/usr/local/src/pgadmin3/src/pgadmin3") at include/wx/strconv.h:55 #27 0x0859cdee in ConvertArgsToUnicode (argc=1, argv=0xbbb4) at src/common/init.cpp:181 #28 0x0859d47e in wxEntry(int&, char**) ([EMAIL PROTECTED], argv=0xbbb4) at src/common/init.cpp:461 #29 0x0819e364 in main (argc=1, argv=0xbbb4) at pgAdmin3.cpp:78 #30 0x40781bb4 in __libc_start_main () from /lib/libc.so.6 (gdb) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] New wx patch
Dave Page wrote: Although I now find that 20031010 hangs in the same way :-( Probably because you're working as root ;-) This might still be a cvs head, not a 20031010 snapshot. There's work going on in the conversion section. For sure, it's a problem in the wx startup code. Regards, Andreas ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] New wx patch
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 27 October 2003 12:59 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] New wx patch > > Dave Page wrote: > > >Although I now find that 20031010 hangs in the same way :-( > > > > > > Probably because you're working as root ;-) > > This might still be a cvs head, not a 20031010 snapshot. > There's work going on in the conversion section. For sure, > it's a problem in the wx startup code. Ack. Typo in the CVS command. 'Tis OK, now - there is a new wx snapshot on Snake. Regards, Dave. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] Need help with GTK bug
Hi Dave. I search for the cause of this problem. Is this helpful? However, a problem is still left.:-( regards, Hiroshi Saito From: "Dave Page" <[EMAIL PROTECTED]> > The bug in question is listed in BUGS.txt as: Menu item 'Query Browser' > causes Segfault under unix - crash after qbForm->Show() in > frmQueryBuilder::OnSize() at layout.LayoutMDIFrame(this). QB currently > disabled. frmQueryBuilder_patch Description: Binary data ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Need help with GTK bug
Hiroshi Saito wrote: Hi Dave. I search for the cause of this problem. Is this helpful? However, a problem is still left.:-( Hm, I doubt that this is helpful in any way, because it just lets some vars uninitialized before Create(), so I assume the current version is better. Regards, Andreas ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] Need help with GTK bug
Hi Andreas. From: "Andreas Pflug" <[EMAIL PROTECTED]> > Hiroshi Saito wrote: > > >Hi Dave. > > > >I search for the cause of this problem. > >Is this helpful? > >However, a problem is still left.:-( > > Hm, I doubt that this is helpful in any way, because it just lets some > vars uninitialized before Create(), so I assume the current version is > better. You are probably right. I thinks that a gtk problem is certain. But,I thinks that the problem can be ascertained by this patch. It takes time a little more to solve it. It is information because Dave may be settled.:-) regards, Hiroshi Saito frmChildTableViewFrame_patch Description: Binary data ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[pgadmin-hackers] Current CVS: Cursor disappears
Hello, In the query window of current pgadmin3 CVS with wxGTK2ud v. wxGTK2ud-2.5-20031010.5 on Red Hat Linux 9 (running GNOME; haven't tried KDE): Initially, a cursor is seen, but if focus is taken away from the window (e.g. by using the mouse or ALT-TAB) and then returned, the cursor is gone. I can still write charaters in the query window, but I have to guess where the characters will be put. If focus is once again taken away from and then returned to the query window, then the cursor re-appears. -- Greetings from Troels Arvin, Copenhagen, Denmark ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
