Hi,
I've just uploaded win32 binaries for wxPython 2.3.3pre4 to Sourceforge.
Both ansi and unicode builds were done this time. YOu can get them at:
http://west.dl.sourceforge.net/wxpython/wxPython-2.3.3pre4-Py22-hybrid.exe
http://west.dl.sourceforge.net/wxpython/wxPython-2.3.3pre4u-Py22-hybrid.exe
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
I've just uploaded win32 binaries for wxPython 2.3.3pre4 to Sourceforge.
Oh yeah, I also moved the wxPy_2_3_3_pre tag in CVS for those of you
building it yourself.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
Ouch! I downloaded the Unicode version. Opened PyCrust. Typed "shell." Got a
command completion list. Typed "h" and then [Tab] and instead of selecting
from the list it set the focus to the namespace tree. 
---
Patrick K. O'Brien
Orbtech
-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Robin Dunn
Sent: Friday, June 07, 2002 1:13 AM
To: wxPython-users
Subject: [wxPython] 2.3.3 preview 4Hi,
I've just uploaded win32 binaries for wxPython 2.3.3pre4 to Sourceforge.
Both ansi and unicode builds were done this time. YOu can get them at:http://west.dl.sourceforge.net/wxpython/wxPython-2.3.3pre4-Py22-hybrid.exe
http://west.dl.sourceforge.net/wxpython/wxPython-2.3.3pre4u-Py22-h
ybrid.exe--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
From the CHANGES.txt file:
"The calltip window and autocomplete window in wxSTC will now use a
wxPopupWindow if available so they can extend beyond the client area of the
STC if needed."
Thank you! I've been meaning to ask for this, but you beat me to it. So, I
still get to make a request, right? <wink>
Is there any way to have the calltip appear below the typed line, unless
there is no room? It seems to prefer to appear above, which is not as nice,
imo.
Thanks.
---
Patrick K. O'Brien
Orbtech
-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Robin Dunn
Sent: Friday, June 07, 2002 1:13 AM
To: wxPython-users
Subject: [wxPython] 2.3.3 preview 4Hi,
I've just uploaded win32 binaries for wxPython 2.3.3pre4 to Sourceforge.
Both ansi and unicode builds were done this time. YOu can get them at:http://west.dl.sourceforge.net/wxpython/wxPython-2.3.3pre4-Py22-hybrid.exe
http://west.dl.sourceforge.net/wxpython/wxPython-2.3.3pre4u-Py22-h
ybrid.exe--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
Is there any way to have the calltip appear below the typed line, unless
there is no room? It seems to prefer to appear above, which is
not as nice, imo.
Actually, it would be nice if both the autocomplete list and calltip had a
strong preference for appearing below the text that triggers them. By that I
mean they should appear below, even if they have to extend beyond the client
area. If extending beyond the client doesn't provide enough room, then they
should appear on top.
Is this doable?
---
Patrick K. O'Brien
Orbtech
>From the CHANGES.txt file:
"The calltip window and autocomplete window in wxSTC will now use a
wxPopupWindow if available so they can extend beyond the client area of
the
STC if needed."
Thank you! I've been meaning to ask for this, but you beat me to it. So, I
still get to make a request, right? <wink>
Actually it's only half there currently. I had to move the autocomplete
window back to NOT use the wxPopupWindow because of some focus and capture
problems on MSW. The calltip window is still implemented with a
wxPopupWindow though.
Is there any way to have the calltip appear below the typed line, unless
there is no room? It seems to prefer to appear above, which is not as
nice,
imo.
It seems to already behave that way, in my tests anyway.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
Ouch! I downloaded the Unicode version. Opened PyCrust. Typed "shell." Got
a
command completion list. Typed "h" and then [Tab] and instead of selecting
from the list it set the focus to the namespace tree.
Oooo, that's a fun one... I'll see what I can do.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
> Is there any way to have the calltip appear below the typed line, unless
> there is no room? It seems to prefer to appear above, which is not as
nice,
> imo.It seems to already behave that way, in my tests anyway.
That's not what I see on Win 98. By that I mean that the call tip will
display above the line instead of extending down over the namespace viewer
in PyCrust standalone.
---
Patrick K. O'Brien
Orbtech
> > Is there any way to have the calltip appear below the typed line,
unless
> > there is no room? It seems to prefer to appear above, which is not as
> nice,
> > imo.
>
> It seems to already behave that way, in my tests anyway.That's not what I see on Win 98. By that I mean that the call tip will
display above the line instead of extending down over the namespace viewer
in PyCrust standalone.
Oh, right. I wasn't thinking "outside the box" <wink!>
I think Scintilla will always try to position them inside the editor window
because everywhere else it is just using simple child windows and not
popups. Neil, is there a way to override the positions?
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
This is another weird focus issue.
With 2.3.3 preview four, when a wxProgressDialog is dismissed/destroyed, the
parent window loses focus and drops behind some other window. For instance
if I launch my application from the command line, when the wxProgressDialog
is dismissed, my application drops behind the shell window I launched it
from. Very odd! Is this a known issue? I haven't taken the time to isolate
it yet, but I will try to put together a minimal test case if this turns out
to be an unknown problem.
Regards,
-tim
Robin Dunn:
Oh, right. I wasn't thinking "outside the box" <wink!>
I think Scintilla will always try to position them inside the editor
window
because everywhere else it is just using simple child windows and not
popups. Neil, is there a way to override the positions?
Well, its just a window 
I don't think Scintilla will move it back if
you grab it and move it wherever you want. There could be an option to
ignore the container window position when deciding where to appear.
The policy is to place the calltip just under the caret unless there is
not enough room in which case it is located above the caret.
Neil
>
> I think Scintilla will always try to position them inside the editor
window
> because everywhere else it is just using simple child windows and not
> popups. Neil, is there a way to override the positions?Well, its just a window
it back if
you grab it and move it wherever you want. There could be an option to
ignore the container window position when deciding where to appear.The policy is to place the calltip just under the caret unless there is
not enough room in which case it is located above the caret.
And I slide it to the left a bit to align the left paren at the caret with
the left paren in the first line of the calltip. Just FYI.
---
Patrick K. O'Brien
Orbtech
Patrick K. O'Brien:
And I slide it to the left a bit to align the left paren at the caret with
the left paren in the first line of the calltip. Just FYI.
In SciTE the parens line up. Maybe its because I'm using an old version
but PyCrust is using the caret position as the positioning argument to the
call tip start method rather than start of the calltip trigger like SciTE
does.
Neil
[Neil Hodgson]
Patrick K. O'Brien:
> And I slide it to the left a bit to align the left paren at the
caret with
> the left paren in the first line of the calltip. Just FYI.In SciTE the parens line up. Maybe its because I'm using an old version
but PyCrust is using the caret position as the positioning argument to the
call tip start method rather than start of the calltip trigger like SciTE
does.
According to CHANGES.txt, I "Improved call tip positioning calculation." in
version 0.7.1. The current code looks like this:
def autoCallTipShow(self, command):
"""Display argument spec and docstring in a popup bubble thingie."""
if self.CallTipActive: self.CallTipCancel()
(name, argspec, tip) = self.interp.getCallTip(command)
if argspec:
startpos = self.GetCurrentPos()
self.write(argspec + ')')
endpos = self.GetCurrentPos()
self.SetSelection(endpos, startpos)
if tip:
curpos = self.GetCurrentPos()
tippos = curpos - (len(name) + 1)
fallback = curpos - self.GetColumn(curpos)
# In case there isn't enough room, only go back to the fallback.
tippos = max(tippos, fallback)
self.CallTipShow(tippos, tip)
---
Patrick K. O'Brien
Orbtech
This is another weird focus issue.
With 2.3.3 preview four, when a wxProgressDialog is dismissed/destroyed,
the
parent window loses focus and drops behind some other window. For instance
if I launch my application from the command line, when the
wxProgressDialog
is dismissed, my application drops behind the shell window I launched it
from. Very odd! Is this a known issue? I haven't taken the time to isolate
it yet, but I will try to put together a minimal test case if this turns
out
to be an unknown problem.
There were some changes done to the progress dialog recently, but I don't
recall right off if it was before or after I did the pre4 build. I'll take
a look at the minimal test if you send it.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
Hi Robin,
Here's a pared down example that illustrates the problem. In the process of
paring it down I discovered what may be a workaround -- if I destroy the
dialog without using Show(0) the change of focus does not occur.
Left clicking on the window that pops up when this runs will display the
progress dialog -- when it goes away, the frame should pop behind some other
window.
-tim
> This is another weird focus issue.
>
> With 2.3.3 preview four, when a wxProgressDialog is dismissed/destroyed,
the
> parent window loses focus and drops behind some other window. For
instance
> if I launch my application from the command line, when the
wxProgressDialog
> is dismissed, my application drops behind the shell window I launched it
> from. Very odd! Is this a known issue? I haven't taken the time to
isolate
> it yet, but I will try to put together a minimal test case if this turns
out
> to be an unknown problem.There were some changes done to the progress dialog recently, but I don't
recall right off if it was before or after I did the pre4 build. I'll
take
progress.py (834 Bytes)
----- Original Message -----
a look at the minimal test if you send it.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
Here's a pared down example that illustrates the problem. In the process
of
paring it down I discovered what may be a workaround -- if I destroy the
dialog without using Show(0) the change of focus does not occur.Left clicking on the window that pops up when this runs will display the
progress dialog -- when it goes away, the frame should pop behind some
other
window.
Definitly weird... Please enter a bug report about this.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!