|
From: Joachim W. <wu...@cr...> - 2002-12-05 14:46:12
|
Sorry for the length of my previous mail,
there is a very short answer to the main question:
plSetOpt("np", ""); // no pause between plots
So, the only task remains to implement this in the Windows binding,
using dev->nextPlot as indicated before.=20
Joachim
> -----Urspr=FCngliche Nachricht-----
> Von: Joachim Wuttke=20
> Gesendet: Donnerstag, 5. Dezember 2002 14:46
> An: plp...@li...
> Betreff: [Plplot-devel] Fundamental program design question: How to
> advance the page ?
>=20
>=20
> In the official plplot examples, the main program is kind of=20
> a batch job,
> as often occurs in numeric applications, and the user=20
> interacts via the
> graphical frontend only: The main program produces one plot, then
> waits for the user to acknoledge. In the MSWindows binding, the user
> has to single-click the right mouse button.=20
>=20
> QUESTION: is this intended, and is similar behaviour=20
> implemented for
> the other operation systems as well ?
>=20
> Now there is another important class of programs which may be called
> dialog-driven, in contrast to the batch programs mentioned=20
> before. In a
> dialog-driven application, the user interacts directly with=20
> the main program,
> and therefore we should be able to erase a page and start=20
> plotting a new
> one without requiring a redundant mouse click.
>=20
> SIDE REMARK: Dialog-driven numeric programs where almost=20
> unheard of when
> pgplot and other predecessors of plplot were designed down in=20
> about the 70's.
>=20
> BACKGROUND QUESTION: Has it ever been discussed how to=20
> support dialog-driven
> applications in a consistent manner within the given overall=20
> design of plplot ?
>=20
> PRACTICAL QUESTION: Which sequence of pleop, pladv, plbop=20
> or similar
> should produce the desired behaviour (full software control=20
> over page advance) ?
>=20
> AD-HOC SOLUTION: Within MSWindows, I helped myself by just setting
> dev->nextPlot =3D 1 instead of 0 at two locations in win3.cpp.=20
> Introducing a
> precompiler macro AUTOADVANCE could formalise this solution.=20
> However, I
> suppose a cleaner solution would be through some pl*** function.
>=20
> Best regards to all, Joachim
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Plplot-devel mailing list
> Plp...@li...
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
>=20
|