Hey all, I've got some good news. Here are a few thousand pictures to tell you all about it: http://wxpython.org/Phoenix/ItsAlive/ -- Robin Dunn Software Craftsman http://wxPython.org -- -- To unsubscribe, send email to wxPython-dev+unsubscribe <at> googlegroups.com or visit http://groups.google.com/group/wxPython-dev?hl=en
Hi, A new test build of wxPython has been uploaded. Version: 2.9.4.0.b20120519 URL: http://wxPython.kosoftworks.com/preview/20120519 Changes: http://wxPython.kosoftworks.com/preview/20120519/CHANGES.html Have fun! R'bot -- -- To unsubscribe, send email to wxPython-dev+unsubscribe <at> googlegroups.com or visit http://groups.google.com/group/wxPython-dev?hl=en
I am extending wx.BitmapButton to include some custom drawing on the bitmap using cairo and I stumbled across what appears to be a bug in the function ImageSurfaceFromBitmap within the wx.lib.wxcairo module. I believe that when creating a surface from a bitmap (within ImageSurfaceFromBitmap) the resulting surface needs to get a mark_dirty() call before returning. The documentation comments: "mark_dirty() tells cairo that drawing has been done to Surface using means other than cairo, and that cairo should reread any cached areas. Note that you must call flush() before doing such drawing." In this case I do not think flush() is needed since the surface is just created - but the mark_dirty() is still needed. See the code below demonstrating: Download smiley.png from: http://upload.wikimedia.org/wikipedia/en/6/6f/Smiley_Face.png smiley_check.png should write back out correctly (oddly this works since it must use the cache) and match smiley.png smiley_fail.png will have the red nose only smiley_succeed.png will have the face with the red nose -------------------------------------------------------------------------- import cairo import wx(Continue reading)
Hi (Robin),
in my current wxPython installation (MSW classic, 2.9.3.1, Windows
Vista 64 bit and Python 2.7.2 64 bit), I get an ImportError if I try
to import wx.ribbon:
>>> wx.VERSION_STRING
'2.9.3.1'
>>> import wx.ribbon
Traceback (most recent call last):
File "<interactive input>", line 1, in <module>
ImportError: No module named ribbon
I guess my installation may be broken, or I may have misunderstood something 
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
--
--
To unsubscribe, send email to wxPython-dev+unsubscribe <at> googlegroups.com
or visit http://groups.google.com/group/wxPython-dev?hl=en
All,
just for the fun of it, I was wondering what it would take to
slowly (and finally) remove the distinction between "stable" and
"unstable" wxWidgets/wxPython releases:
http://wiki.wxpython.org/ReleaseSeries
As a starter, due to the veeeeeeeery long release schedule of
wxWidgets, I would say that the whole concept of stable/unstable is
somehow meaningless: wxPython 2.8 was released in December 2006, and
there is no firm plan for a 3.0 release as far as I can see. I agree
that there have been many "release series" of wxWidgets 2.8 (i.e., the
third number after the second dot in the wx version string), but then
again how long has it been since the changes in 2.9 have been
back-ported to 2.8? The only messages I have seen on wx-dev and
wx-users during the last few months made plain clear that the main
developers were not interested anymore in back-porting
enhancements/bug fixes to 2.8 (and there is still no 3.0 in sight).
If dropping the "stable" / "unstable" pair is not an option, how about
changing the wording for the description of the odd/even releases? OK,
maybe 2.7 or 2.9 did change a parameter in one method or broke the API
compatibility for another one, but is it such a big deal to label a
release as "unstable"? The very wording of it can easily intimidate
someone who wishes to migrate his/her app to a newer
wxWidgets/wxPython version, not to mention the various Linux
distributions which refuse to provide a build for 2.9 because it's
"unstable" (yeah, right).
(Continue reading)
http://trac.wxwidgets.org/ticket/4099#comment:3 http://wxpython-users.1045709.n5.nabble.com/StaticBitmap-sunken-border-eats-into-image-size-td2351410.html Still a bug as of wx.version() '2.8.11.0 (msw-unicode)' -- -- To unsubscribe, send email to wxPython-dev+unsubscribe <at> googlegroups.com or visit http://groups.google.com/group/wxPython-dev?hl=en
Hi,
Im trying to make a program where the user can draw on a transparent
frame and dc, which creates the effect of drawing on the desktop.
However the dc's DrawLine method seems to also draw a filled
rectangle around the line which is an image of the desktop showing
behind the line, so when the frame is moved, so does the line and
image.
At the moment, I am using a custom line drawing algorithm which draws
many squares in the line, this method is very inefficient.
Is there any way of making the backgrounds of things drawn on a dc
transparent like the rest of the dc?
Here is an example of what i mean:
import wx
import math
class OverlayFrame(wx.Frame):
"""This is the transparent frame that overlays the application and
recieves mouse input when painting (application feature) is enabled
and sends it to the DC for display."""
def __init__(self, parent):
self.last_pos = wx.Point(0, 0)
wx.Frame.__init__(self, parent, title = "", size = (1000,
1000), style = wx.CLIP_CHILDREN | wx.CLIP_CHILDREN | wx.NO_BORDER |
wx.FULL_REPAINT_ON_RESIZE)
self.Bind(wx.EVT_ERASE_BACKGROUND, self.OnEraseBackground)
self.Bind(wx.EVT_LEFT_DOWN, self.OnLeftDown )
self.Bind(wx.EVT_MOTION, self.OnMotion )
(Continue reading)
Folks,
I just tried to get wxPython2.9 working with a wxmpl- based app (wxmpl
is a library for embedding Matplotlib in wx apps). It crashed out on
me with:
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/wxmpl.py",
line 1127, in __init__
topwin.Connect(-1, self.GetId(), wx.wxEVT_ACTIVATE, self.OnActivate)
File "/usr/local/lib/wxPython-2.9.3.1/lib/python2.7/site-packages/wx-2.9.3-osx_carbon/wx/_core.py",
line 4184, in Connect
return _core_.EvtHandler_Connect(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "idLast == wxID_ANY || winid
<= idLast" failed at
/BUILD/wxPython-src-2.9.3.1/include/wx/event.h(2875) in
wxEventTableEntryBase(): invalid IDs range: lower bound > upper bound
I've isolated the issue, and made the simple enclosed sample app:
If you try to call Connect, with an ID generated by using wx.ID_ANY,
it fails with:
wx._core.PyAssertionError: C++ assertion "idLast == wxID_ANY || winid
<= idLast" failed at
/BUILD/wxPython-src-2.9.3.1/include/wx/event.h(2875) in
wxEventTableEntryBase(): invalid IDs range: lower bound > upper bound
if seems that there is an issue with negative IDs -- when I pass in
wx.ID_ANY, the panel gets the
ID: -2007. If I explicitly give the panel an ID (like 100) it works
(Continue reading)
Hi all, Just a quick note to let you know that I've been working on getting the Phoenix buildbot doing more for us than just a simple build on a single platform. It's now got build slaves on OSX, Windows and Ubuntu. I've also added builders that will run once daily for making a tarball with binaries for OSX[1] and Windows, and also a once daily builder that will build the docs[2] and make a tarball of them. You can view the buildbot waterfall, build logs, etc. at http://buildbot.wxpython.org:8010. The tarballs are uploaded to http://wxpython.org/Phoenix/snapshot-builds/ after they have been created. [1] There are no new OSX binaries on the server yet as that build slave had a problem which has just been resolved. I'll trigger a new dist build once the current normal build succeeds. [2] Just the docs for the core modules are being built so far since wx.lib and etc. hasn't been copied into the Phoenix source tree yet. -- Robin Dunn Software Craftsman http://wxPython.org -- -- To unsubscribe, send email to wxPython-dev+unsubscribe <at> googlegroups.com or visit http://groups.google.com/group/wxPython-dev?hl=en(Continue reading)
On 4/7/12 3:17 PM, noreply <at> wxsite.net wrote:
> # The SVN revision of wxWidgets/Phoenix used to build the Sphinx docs.
> # There must be a more intelligent way to get this information automatically.
> -SVN_REVISION = '71066'
import subprocess
svn_result = subprocess.Popen(["svn", "info"],
stdout=subprocess.PIPE).communicate()[0]
REV = 'unknown'
for line in svn_result.split("\n"):
if line.startswith("Revision"):
REV = line.split(":")[-1].strip()
break
# Do something with REV, like write it to constants.py
--
Robin Dunn
Software Craftsman
http://wxPython.org
--
--
To unsubscribe, send email to wxPython-dev+unsubscribe <at> googlegroups.com
or visit http://groups.google.com/group/wxPython-dev?hl=en
Hi All,
as an Easter present, I am happy to release a new set of
documentation pages for Phoenix, which is available here:
http://xoomer.virgilio.it/infinity77/Phoenix/main.html
I have managed to run the whole of Phoenix, wx.lib, wx.py and wx.tools
via Sphinx - basically everything we have in wxPython.
Also, most (if not all) the Epydoc docstring hyperlinks which are
present in Editra, XRCed and in some place else (i.e., the ones with
L{something}, U{something}, C{something} and so on) are automatically
handled by the docstrings scanner, so you will see most of them
converted to proper links in the HTML documentation.
Werner, I have updated the I18N sample to the latest specs.
There is still some work to do, of course, especially on improving the
docstrings themselves in wx.lib and wx.tools. Editra is well
documented but the automatic sphinx_generator tool can't possibly
convert, without sometimes failing, docstrings that are meant for
Doxygen to Sphinx-compliant ones.
Cody, do you mind me making some slight changes to the docstrings in
Editra or will you prefer a patch against the latest SVN version?
In any case, I think the overall result is good (and with only 70
warnings from Sphinx...). Please let me know if you find anything
strange, and also your thoughts on possible modifications, additions,
(Continue reading)
RSS Feed23 | |
|---|---|
62 | |
92 | |
34 | |
17 | |
67 | |
68 | |
49 | |
83 | |
5 | |
6 | |
8 | |
27 | |
9 | |
5 | |
11 | |
56 | |
26 | |
88 | |
67 | |
53 | |
49 | |
15 | |
14 | |
17 | |
16 | |
15 | |
30 | |
51 | |
52 | |
12 | |
5 | |
3 | |
15 | |
26 | |
33 | |
16 | |
49 | |
44 | |
41 | |
32 | |
3 | |
15 | |
36 | |
22 | |
24 | |
42 | |
69 | |
29 | |
25 | |
39 | |
4 | |
23 | |
14 | |
93 | |
41 | |
40 | |
32 | |
35 | |
24 | |
73 | |
34 | |
40 | |
10 | |
20 | |
50 | |
38 | |
103 | |
80 | |
15 | |
53 | |
18 | |
11 | |
12 | |
19 | |
40 | |
110 | |
48 | |
35 | |
20 | |
47 | |
9 | |
11 | |
33 | |
68 | |
111 | |
101 | |
51 | |
27 | |
40 | |
77 | |
208 | |
154 | |
127 | |
94 | |
104 | |
81 | |
66 | |
44 |
