RE: [Plplot-devel] Help with plD_dispatch_init_win3 needed

[Geoffrey F. <fu...@ga...>]

Olof Svensson writes:
 > Hi plplot developers,
 > 
 > as you have noticed I'm working on getting the Win32 port of plplot
 > working again. I noticed that since the 5.0.4 release a new function is
 > needed for the win3 device, i.e. the "plD_dispatch_init_win3" function.
 > I copied the one I found in "ps.c" and I got the win3 device working
 > however I have no idea if I'm using the correct values:
 > 
 > win3_dispatch_init_helper( pdt,
 >                            "PlPlot Win32 Window", 
 >                            "win3",
 >                            plDevType_FileOriented, 
 >                            29,
 >                            (plD_init_fp) plD_init_win3 );
 > 
 > For example, is it right to use "plDevType_FileOriented" and the pl_seq
 > number 29?

Thanks for working on updating the Win32 port.

The available driver types are shown in disptab.h:

enum {
    plDevType_FileOriented = 0,
    plDevType_Interactive = 1,
    plDevType_Null = -1
};

I /assume/ you want plDevType_Interactive, but I've never looked into
using PLplot on windows, so I can't be certain.

From plcore.h, I find that the old seq # for the win3 driver was 10.
I would preserve that one on the assumption that it made sense, unless
you have a particular reason to push it down the stack.  In general I
think the rule is to get the sequence number of the drivers ordered so
that the default interactive driver for each platfrom will be the top
one listed in the display.  Dunno if that's strictly possible since
there are numerous possible interactive drivers on some platforms, and
whose to say which one is the best default, but that's at least the
general idea.  The file oriented drivers show up lower on the list.

The master registry of seq numbers is not at all clear right now,
sorry.  We should somehow formalize this better.  Maybe an enum for
the driver sequencing id defined somewhere, I'm not sure what's best.
Anyway, there's an "#if 0/#endif" block in plcore.h, which I left
there so we can refer to it as we update all the driver code.  Someday
that should be summarily expunged, but I think someone should dump a
little effort into formalizing the device sequencing registry before
we take that final step.

I am not volunteering, so if anyone is inclined, go ahead.

-- 
Geoffrey Furnish         fu...@ga...