Alan W. Irwin wrote:
> On 2008-10-08 11:31+0200 Robert Pollak wrote:
>
>> Hi Alan, Arjen,
>>
>> Alan wrote:
>>
>>> Robert, what happens if you add
>>>
>>> #define PLDLLEXPORT
>>> #define PLDLLIMPORT
>>>
>>> to the #else stanza above? I predict that will fix your problem with
>>> the -DBUI
Alan W. Irwin wrote:
> On 2008-10-08 12:56+0200 Robert Pollak wrote:
>
>>> D:\project\PLPlot\drivers\svg.c(341) : error C2143: syntax error :
>>> missing ';' before 'type'
>>
>> This is fixed by simply removing the unused "int i;" line.
>> Can someone please commit this change?
>
> I have no idea w
Hi list,
(Hi Werner Smekal, I am CCing you as the maintainer of the PLplot
wxWidgets driver.)
I am using Windows XP, Visual Studio 2008 Express Edition and cmake-2.6.2.
I have built PLplot revision 8864 with the
following batch file in the PLPlot root folder:
= begin
echo on
se
Hi,
sorry, that I (again) kick in late in this discussion, but this change
was not the right solution. Actually, the macros PLDLLEXPORT/
PLDLLIMPORT are not to be used outside pldll.h. Only PLDLLIMPEXP
should be used in headers and source. This was correctly done for the
plplot core source,
Alan W. Irwin wrote:
> Could you also confirm you are using ENABLE_DYNDRIVERS=OFF? (I think
> that result will happen by default since libltdl is not readily
> available on Windows. You should get a WARNING message from cmake
> about that.)
Yes, In the static build cmake says
"WARNING: Shared l
Hi Robert,
> I have built PLplot revision 8864 with the
> following batch file in the PLPlot root folder:
>
> = begin
> echo on
> setlocal
>
> call "%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\Tools
> \vsvars32.bat"
>
> rem Debug or Release:
> set BUILD_TYPE=Debug
>
> set
Hi Robert:
Two points of information for you below.
> (Btw, the library names do not differ between Debug and Release build:
> plplotd.*, plplotcxxd.*, csirocsa.*. So the "d" ending is misleading.)
For PLplot, the "d" stands for the double-precision version. You can build
a single-precision ver
On 2008-10-09 16:42+0200 Werner Smekal wrote:
> Hi,
>
> sorry, that I (again) kick in late in this discussion, but this change was
> not the right solution. Actually, the macros PLDLLEXPORT/PLDLLIMPORT are not
> to be used outside pldll.h. Only PLDLLIMPEXP should be used in headers and
> source
On Thu, Oct 09, 2008 at 08:44:34AM -0700, Alan Irwin wrote:
> On 2008-10-09 16:42+0200 Werner Smekal wrote:
>
> > Hi,
> >
> > sorry, that I (again) kick in late in this discussion, but this change was
> > not the right solution. Actually, the macros PLDLLEXPORT/PLDLLIMPORT are
> > not
> > to be
What started me thinking about how to support gradients within PLplot is the
large PLplot logo at the top of our webpage which is smoothly darkened on
the left. I don't know how Werner created that effect, but it is unlikely
to be within PLplot because we currently don't support gradients. Instea
Hi Andrew,
> This may not be quite the right long term solution. Language bindings
> for example might be importing some symbols from the core library and
> exporting others to the user. Similarly for drivers.
Sure. Ok, I rephrase: this is the correct solution as it was initially
considered, bu
On Thu, Oct 09, 2008 at 09:09:47PM +0200, Werner Smekal wrote:
> Hi Andrew,
>
>
> > This may not be quite the right long term solution. Language bindings
> > for example might be importing some symbols from the core library and
> > exporting others to the user. Similarly for drivers.
>
> Sure. O
Hi Alan,
this would actually be a nice addition to the plplot library, to also
make it more modern. Look for example at
http://www.scilab.org/publications/JARAUSCH/PinconD.pdf
on page 84 (document is in German). The colors of the 3d plot on the
right are interpolated and this looks actually qu
On 2008-10-09 20:39+0100 Andrew Ross wrote:
> It's not quite a cmake issue since we need xxxMAKINGDLL for the driver
> source file and xxxUSINGDLL for the core header files included by the
> source file. At the moment these are mutually exclusive so we can't do
> it with just cmake options. It wil
On 2008-10-09 21:44+0200 Werner Smekal wrote:
> Hi Alan,
>
> this would actually be a nice addition to the plplot library, to also make it
> more modern. Look for example at
>
> http://www.scilab.org/publications/JARAUSCH/PinconD.pdf
>
> on page 84 (document is in German). The colors of the 3d pl
On Thu, Oct 09, 2008 at 03:17:40PM -0700, Alan Irwin wrote:
> On 2008-10-09 20:39+0100 Andrew Ross wrote:
>
> > It's not quite a cmake issue since we need xxxMAKINGDLL for the driver
> > source file and xxxUSINGDLL for the core header files included by the
> > source file. At the moment these are
On Thursday, October 9, 2008 at 12:04:56 (-0700) Alan W. Irwin writes:
> ...
> Note, the question of PLplot support for gradients has internal core library
> implications (e.g., triangle representation for surfaces), API implications
> (what is the most convenient way to let PLplot users specif
On Monday, September 29, 2008 at 16:27:56 (-0400) Hezekiah M. Carty writes:
> Would it be possible to add an internal function, not exposed in the
> official API, which applies the transform itself, while keeping the
> actual plsc->vpw* values unaltered from what the user provides?
>
> Lookin
> On Thu, Oct 09, 2008 at 03:17:40PM -0700, Alan Irwin wrote:
> It is. Setting xxxUSINGDLL for the drivers ensures that all the
> symbols from the core library defined in plplot.h etc are imported into
> the driver. This is ok. However, there are some symbols in the driver
> files which are exporte
On Saturday, October 4, 2008 at 16:46:53 (-0700) Alan W. Irwin writes:
> On 2008-10-04 14:04-0700 Alan W. Irwin wrote:
>
> > Hi Maurice:
> >
> > I have just committed my first attempt (see src/README.pages) to annotate
> > all the code fragments in our source code that affect paging and fami
On Thursday, October 9, 2008 at 23:42:11 (-0500) Maurice LeBrun writes:
> On Saturday, October 4, 2008 at 16:46:53 (-0700) Alan W. Irwin writes:
> > On 2008-10-04 14:04-0700 Alan W. Irwin wrote:
> >
> > > Hi Maurice:
> > >
> > > I have just committed my first attempt (see src/README.pag
Arjen said:
> If I understand the issue of IMPORT/EXPORT correctly, then:
> - EXPORT is always necessary to make the function visible
> outside the DLL.
> - IMPORT is used to tell the linker that the function is coming
> from another library, so that it can prepare for a faster call
> (otherwis
Alan W. Irwin wrote:
>
> I suggest you simplify the above logic by separating the driver namespace
> from the core library one just as we currently do for the csa and nn
> libraries. What I had in mind was using MAKINGDRDLL, USINGDRDLL,
> DRDLLEXPORT, DRDLLIMPORT, and DRDLLIMPEXP for the driver-re
On 2008-10-09 23:42-0500 Maurice LeBrun wrote:
> On Saturday, October 4, 2008 at 16:46:53 (-0700) Alan W. Irwin writes:
> > I made the empty-page fix, and indeed that fixed the example 23 issue for
> > the pages which consisted just of text (see my recent post on the svg
> > status). However, in
Hi,
I just admitted lot of changes to get this import/export issue right.
What I basically did I explain in pldll.h:
#ifndef __PL_DLL_H
#define __PL_DLL_H
This is now different. We only get into this part of the header fil
On 2008-10-09 23:47-0500 Maurice LeBrun wrote:
> To be clear, the latter statement means a primary goal of AT_BOP and AT_EOP
> was to suppress empty pages that crept into the plotting session by mistake
> or sloppy programming. That's not been changed overall, correct?
Correct. To see exactly w
26 matches
Mail list logo
