On Mar 11, 2015, at 6:49 AM, "Alan W. Irwin" <ir...@beluga.phys.uvic.ca> wrote:
> On 2015-03-10 21:41-0000 Phil Rosenberg wrote: > >> Hi Alan and Jim >> Right, well Jim's patch series is committed and I have just made one >> more additional commit regarding the buffer which I think now gives us >> a buffer which is (pretty close to, if not completely) bug free!!! Or >> at the very least it is sufficient to allow the wxWidgets driver to >> render as well as from direct commands. > > Note, to everybody. There is an official deep freeze notice near > the end of this e-mail. > > @ Andrew, Phil, and Jim: > > Before getting to wxwidgets test results I regret to say that a recent > plbuf change has nailed us again. There is now a release showstopper > where -dev tk produces really strange looking results. I found this > issue via checking -dev tk for the zoom regression where hitting the > zoom button just produces a blank (black) plot. I confirm that > regression as well as a newly introduced regression for that device > (two windows are displayed rather than one with one of them without a > plot but with the plframe decorations and the other showing an > xwin-like plot windows with no decorations). This new regression and > the zoom regression are showstoppers for the current release so your > confirmation and fix for these rendering regressions will be much > appreciated. You should also look carefully at -dev wingcc to see > whether recent plbuf changes have introduced rendering regressions > there as well (assuming you have looked in detail before at wingcc > results for all examples, and therefore know what rendered nicely in > the old days). > I cannot replicate this problem. I was able to zoom by pressing "z" and zoom out with "b" and nothing happened with "f". > > @Everybody: > > To make this decision official, this is notice from your release manager > that we are now in deep freeze until release. That is, only > documentation changes and small and _very well tested_ fixes should be > pushed to master during this deep freeze. In particular, because > plbuf changes have such a wide impact, I ask everyone here to avoid > commits to master that involve any plbuf changes at all during deep > freeze unless such commit can be shown to fix a non-wxwidgets > rendering regression caused by an earlier plbuf change in this release > cycle. > > Also, despite the extra effort we are going to need to deal with the > rendering regressions, I do honestly want to thank both Phil and Jim > for all their hard work on wxwidgets/plbuf that has finally gotten us > to the point where we can declare a deep freeze. That's a really > important goal for late in a release cycle, and I am really glad we > have finally achieved that goal! > Attached is a patch series that reverses a change that Phil made to restore static to plhrsh. I recalled incorrectly on its use by plmetafile.c and it is needed to compile without error. At this point there is no way around exposing plhrsh(). Sorry for the confusion.
fix-plhrsh-for-plmetafile.patch
Description: Binary data
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
