|
From: Joachim W. <wu...@cr...> - 2002-12-12 17:27:42
|
Now I really need your help:
plSetOpt("drvopt", "<name>=3D<value>");
works only once. If I use it a second time to transmit
a second driver-dependent option, I obtain nonsense
values.
Who is able to disentangle the option-setting mechanism
(and to propose me an ad-hoc solution...) ???
Btw a fundamental question: do we really want the drvopt
keyword ? As far as I see, there are also driver-dependent
options (e.g. for X windows) in what is now formally the
driver-independent section preceeding that keyword.
Joachim
|