Hi Phil, Alan
I started a new thread, that summarizes all the learnings we have so far on
this and proposes a simple solution that keeps the current API (templates).
1) remotely or in place
First the issue of accessing the machine remotely or in place.
One of my machines that I previously
On 2016-12-27 23:41- p.d.rosenb...@gmail.com wrote:
> Hi Laurent
> I know you have said you have cleaned and you have rebuilt. However, there
> may be a build tree dependency issue catching us out. Can you ensure you
> specifically rebuild the wxPlviewer project by right clicking it and
>
Hi phil
I have already check it :
I have clean only wxPlLiewer and run x04 (click on x04) in cmd window I
have :
Plotting Options:
< 1> ps PostScript File (monochrome)
< 2> pscPostScript File (color)
< 3> xfig Xfig file
< 4> null Null device
< 5> mem
Hi Phil
The removal of the templates does not need to be done after all.
see my email from
today 2.46 PM "Infinite Yielding issue"
that has a git patch or my
3.16PM email that has the actual source code files.
I'll send more details, once we get all in sync in communication.
-Pedro
Hi Phil:
You have made many good points. For example, I wholeheartedly second
your comment "In particular, I'm hugely grateful Pedro for your
efforts on this." Also, I completely agree with you it is bad to even
attempt to release anywhere near the Christmas holidays. My
apologies for getting
Hi Laurent
I know you have said you have cleaned and you have rebuilt. However, there may
be a build tree dependency issue catching us out. Can you ensure you
specifically rebuild the wxPlviewer project by right clicking it and selecting
build in visual studio? If you just right click an
This is really brief, I think we are all getting a little overexcited here very
close to the release date.
This is a functionality reducing, backwards incompatible API change. I know for
one that it will not only cause build errors in some of my code, but because I
use wxPLplotwindow classes
What?
I haven't been able to keep up with all the emails as I have had family
commitments over the holiday period, but that's a very large change of the API
that needs some careful consideration. I can't grab the latest source right
now. But what has it changed to if it's no longer templated?
I am using wxwidgets 3.1 built with Visual Studio 2015 and plplot from the
master branch
and using cmake with
cmake ".." -G "Visual Studio 14" -DPL_DOUBLE:BOOL=ON
-DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug"
-DCMAKE_BUILD_TYPE:STRING="Debug" -DBUILD_SHARED_LIBS:BOOL=OFF
Which version of wxwidgets do you use (can you give last commit using
git log)?
Le 27/12/2016 à 22:29, Pedro Vicente a écrit :
>> error is still here. Now what patch should I apply?
>
> there is no patch for the scale issue.
> the patch I send previously on the subject "Using wxWidgets" is for
> error is still here. Now what patch should I apply?
there is no patch for the scale issue.
the patch I send previously on the subject "Using wxWidgets" is for the
issue regarding the use
of templates. To test that, add and replace the 2 attached files on
that email to the master you just did
I always clean my build repo and my cmake cache. Now to be sure I have
just clone plplot in another folder :
$ git clone git://git.code.sf.net/p/plplot/plplot
Cloning into 'plplot'...
remote: Counting objects: 91527, done.
remote: Compressing objects: 100% (29963/29963), done.
remote: Total
On 2016-12-27 15:27-0500 Pedro Vicente wrote:
> ah, yes, that's right "Visual Studio 14" only is for 32 bits
>
> I did not try with 64 bits libs
@Laurent:
Just to interject here, before getting too deeply into 64-bit versus
32-bit Windows differences between Pedro and you, it is important you
ah, yes, that's right "Visual Studio 14" only is for 32 bits
I did not try with 64 bits libs
On 2016-12-27 15:19, Laurent Berger wrote:
> No i think Visual Studio 14 is for 32 bits. Visual Studio 14 win 64
> is for 64 bits libs. I don't use 32 bits libs. All my project are for
> 64 bits
No i think Visual Studio 14 is for 32 bits. Visual Studio 14 win 64 is
for 64 bits libs. I don't use 32 bits libs. All my project are for 64
bits platform. Have you checked x04 with 64 bits libs?
Le 27/12/2016 à 21:11, Pedro Vicente a écrit :
>>> "Visual Studio 14"
>> Does it mean that you use
Laurent
my mistake, the .gz file has a git patch.
Use the attached files to replace the ones you have in git master
-Pedro
On 2016-12-27 15:08, Pedro Vicente wrote:
Hi Laurent
I did some changes to the current master that will allow you to keep
using this code
wxPLplotwindow *frame = new
>> "Visual Studio 14"
> Does it mean that you use 32 bits libs?
No, it means to use Visual Studio 2015 ("Visual Studio 14" is the
version number of Visual Studio 2015)
On 2016-12-27 15:05, Laurent Berger wrote:
> Does it mean that you use 32 bits libs?
>
>
> Le 27/12/2016 à 21:00, Pedro
Hi Laurent
I did some changes to the current master that will allow you to keep
using this code
wxPLplotwindow *frame = new wxPLplotwindow();
would you mind giving it a try?
do
git clone of Plplot (in Windows I use Tortoise git)
extract the attached .gz
copy the 2 files
wxPLplotwindow.h
Does it mean that you use 32 bits libs?
Le 27/12/2016 à 21:00, Pedro Vicente a écrit :
> "Visual Studio 14"
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org!
@Alan
> So if users stick with the old way of
> creating frame they will get a build error
yes
However, there is something we could try, which is,
keep the current way of wxPLplotwindow beging a template,
and at the same time overriding the Create() function (with template).
this could mean
On 2016-12-27 11:29+0100 Laurent Berger wrote:
> Thanks for your answer.
>
> I give you all command I done. I work on master (I made a copy on my previous
> folder). I build plplot in static using vs2015.
>
> When I run x04 example problem is still here. Example seems slower now. I
> think that
On 2016-12-27 10:09-0500 Pedro Vicente wrote:
> @Alan
>
>> Isn't that loss of functionality by definition a backwards
>> incompatibility in the API for the plplotwxwidgets library?
>
> yes
>
> but for the current (5.11.1) release compared to the new implemented
> examples,
> the effect is the
Problem is my compiler said
3>c:\users\laurent.pc-laurent-visi\documents\visual studio
2013\wxopencv\wxopencvmain\courbeplplot.h(55): error C2059: syntax error
Now syntax error I need two days to change my code. It was like this in
previous version of plplot. I don't remember 5.xx.xx. I
Laurent
> I have installed last version of plplot and last patch (from pedro).
> Can
> you confirm me that wxPLplotwindow is now a non template class?
yes, that is correct.
-Pedro
On 2016-12-27 10:04, Laurent Berger wrote:
> Hi,
>
> I have installed last version of plplot and last patch
@Alan
> Isn't that loss of functionality by definition a backwards
> incompatibility in the API for the plplotwxwidgets library?
yes
but for the current (5.11.1) release compared to the new implemented
examples,
the effect is the same
previously the way to start the demo was
wxPLplotwindow
Hi,
I have installed last version of plplot and last patch (from pedro). Can
you confirm me that wxPLplotwindow is now a non template class?
thanks for yours answers
--
Check out the vibrant tech community on one of
Thanks for your answer.
I give you all command I done. I work on master (I made a copy on my
previous folder). I build plplot in static using vs2015.
When I run x04 example problem is still here. Example seems slower now.
I think that I applyed patch because legend are good now but axis
27 matches
Mail list logo
