20040901 test build uploaded

Hi,

A new test build of wxPython has been uploaded to starship.

   Version: 2.5.2.9p.20040901
   URL: http://starship.python.net/crew/robind/wxPython/daily/20040901

Have fun!
R'bot

Hi Robin, err, I mean R'bot, :wink:

When you upload daily builds and report them to wxPython-dev (I noticed you don't post notices everyday), does that mean you're getting ready for a new wxPython build and want to get more testing in, or are you just doing it periodically for those who want to test or use the latest and greatest? Either way is fine, of course, I just want to know if these notices of build uploads are a <wink, wink, nudge, nudge> of a new wxPython release around the bend. :wink:

Thanks,

Kevin

···

On Sep 1, 2004, at 9:25 PM, R'bot wrote:

Hi,

A new test build of wxPython has been uploaded to starship.

   Version: 2.5.2.9p.20040901
   URL: http://starship.python.net/crew/robind/wxPython/daily/20040901

Have fun!
R'bot

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org

have you looked at:
http://starship.python.net/crew/robind/wxPython/daily/20040901/CHANGES.html

<wink, wink, nudge, nudge>
<whispering>
2.5.2.9
</whispering>

···

On Wed, 1 Sep 2004 22:16:33 -0700, Kevin Ollivier <kevino@tulane.edu> wrote:

Hi Robin, err, I mean R'bot, :wink:

When you upload daily builds and report them to wxPython-dev (I noticed you don't post notices everyday), does that mean you're getting ready for a new wxPython build and want to get more testing in, or are you just doing it periodically for those who want to test or use the latest and greatest? Either way is fine, of course, I just want to know if these notices of build uploads are a <wink, wink, nudge, nudge> of a new wxPython release around the bend. :wink:

--
Peter Damoc
Hacker Wannabe
http://www.sigmacore.net/

Peter Damoc writes:

have you looked at:
http://starship.python.net/crew/robind/wxPython/daily/2004090
1/CHANGES.html

Robin, perhaps if you could put the link to CHANGES.html in the
notifications of test builds... I know I would read them!
Either that, or put a text version in the notification itself,
but only for the most recent version.

···

--
Paul McNett
Independent Software Consultant
http://www.paulmcnett.com

Kevin Ollivier wrote:

Hi Robin, err, I mean R'bot, :wink:

When you upload daily builds and report them to wxPython-dev (I noticed you don't post notices everyday),

Yeah, I still havn't installed a cron job to do it daily, but even then it would be a not-quite-daily build as it will stop the whole process upon any error on any of the build platforms.

does that mean you're getting ready for a new wxPython build and want to get more testing in, or are you just doing it periodically for those who want to test or use the latest and greatest?

This time it is just the former. I had promised to get a test build done with the new ogl.DrawShape included so that is what drove this build. Sometimes though it will be a <wink, wink, nudge, nudge>, you'll just have to guess which is which :wink:

Actually, my intent is to do the test builds on a semi-regular basis, and then announce here when I'm planning on a release.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Paul McNett wrote:

Peter Damoc writes:

have you looked at:
http://starship.python.net/crew/robind/wxPython/daily/2004090
1/CHANGES.html

Robin, perhaps if you could put the link to CHANGES.html in the notifications of test builds... I know I would read them!

So you need only one click access and can't handle two? :wink: I suppose I can do that.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

I'm some kind of a preview junkie... a daily wxpython might be an overdose... :slight_smile: well, that's life... we shall see. :slight_smile:

···

On Thu, 02 Sep 2004 08:30:18 -0700, Robin Dunn <robin@alldunn.com> wrote:

Kevin Ollivier wrote:

Hi Robin, err, I mean R'bot, :wink:
When you upload daily builds and report them to wxPython-dev (I noticed you don't post notices everyday),

Yeah, I still havn't installed a cron job to do it daily, but even then it would be a not-quite-daily build as it will stop the whole process upon any error on any of the build platforms.

--
Peter Damoc
Hacker Wannabe
http://www.sigmacore.net/

Robin Dunn writes:

So you need only one click access and can't handle two? :wink:

Forgive my excesses, I am but a lowly acolyte. <g>

I suppose I can do that.

Thanks, anything to make it easier to determine, at a glance, if
I want to try out the new test build or wait for the next one.
I realize you want us to try out all of them, and I would do
that if I could, but I just don't have time in my day for that
unfortunately.

I suppose I could have a cronjob start a script every night,
check for new test builds, build it for me and then send me an
email notifying me... and then I can send changes.txt in that
email to myself. Nah, I'm just too lazy. :slight_smile:

···

--
Paul McNett
Independent Software Consultant
http://www.paulmcnett.com

OK, that'd be cool. Since I'm typically working with CVS, I wasn't sure if I should be testing each build that comes along or if I can just wait until a release is nearing to test the build.

BTW, checking the "Changes.html" for the latest version, wasn't it decided that stock buttons get created by default when *both* the stock ID and stock label were specified? If I'm not mistaken about that, I think it's important to note it so that people realize they don't need to change their code if they use the stock ID and label already.

Will let you know if I come across any problems! :wink:

Thanks,

Kevin

···

On Sep 2, 2004, at 8:30 AM, Robin Dunn wrote:

Kevin Ollivier wrote:

Hi Robin, err, I mean R'bot, :wink:
When you upload daily builds and report them to wxPython-dev (I noticed you don't post notices everyday),

Yeah, I still havn't installed a cron job to do it daily, but even then it would be a not-quite-daily build as it will stop the whole process upon any error on any of the build platforms.

does that mean you're getting ready for a new wxPython build and want to get more testing in, or are you just doing it periodically for those who want to test or use the latest and greatest?

This time it is just the former. I had promised to get a test build done with the new ogl.DrawShape included so that is what drove this build. Sometimes though it will be a <wink, wink, nudge, nudge>, you'll just have to guess which is which :wink:

Actually, my intent is to do the test builds on a semi-regular basis, and then announce here when I'm planning on a release.

Kevin Ollivier wrote:

BTW, checking the "Changes.html" for the latest version, wasn't it decided that stock buttons get created by default when *both* the stock ID and stock label were specified? If I'm not mistaken about that, I think it's important to note it so that people realize they don't need to change their code if they use the stock ID and label already.

If the stock ID is given then it will be a stock button if either the label is empty, or the given label matches the stock label. I'll add a note.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi,

I was able to build and run Chandler with this first v2.5.2.9 preview. I had to add NULL-deref checks in wxWindow::Freeze and wxWindow::Thaw on the m_peer member variable. It's possible that the NULL m_peer was a consequence of the bad WxDC calls in Chandler that I haven't yet converted the Rect and Point arguments.

Regards,
David S.

David Surovell wrote:

Hi,

I was able to build and run Chandler with this first v2.5.2.9 preview. I had to add NULL-deref checks in wxWindow::Freeze and wxWindow::Thaw on the m_peer member variable. It's possible that the NULL m_peer was a consequence of the bad WxDC calls in Chandler that I haven't yet converted the Rect and Point arguments.

Freeze and Thaw shoudln't have anything to do with the DC args. Were Freeaw and Thaw called before wxWindow::Create?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

Freeze and Thaw shoudln't have anything to do with the DC args. Were Freeze and Thaw called before wxWindow::Create?

To be honest, I'm not sure of the context in which Freeze and Thaw were called, but they showed up in the crash log and adding the NULL-deref checks fixed the crash.

Regards,
David S.