[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] XaAES palette colour handling

> Why did you touch this piece of code? Because it doesn't work with your
> oVDI I suppose. Hmm, I also needed to change many things in the ARAnyM
> fVDI driver for that. Please read that code again and try to understand

 Ok, I have reread that source, and now I'm more confused than ever. I
though that palettes set on one workstation should not affect any other
workstations (except that it does in CLUT modes). Lets assume from now on
that we're talking about non-clut modes. Under such circumstances,
changing the first 16 pens will not affect other workstations (or other
apps), but still it renders concepts such as desktop themes useless. Do
you want that? And now the thing I'm confused about;

 You open a workstation, you modify the palette on this workstation, and
you close it again? I must have missed something here, because if not, I
dont have a clue how VDI should handle virtual (or local to the owners
apps) resources. oVDI, when in non-clut modes, keeps a separate palette
for each virtual workstation that is opened. In effect, changing the
palette like in LoadResource, then close the virtual, is a vaste of time.
I just cannot believe that changing, lets say, color 23 of one virtual
should change this colour of all other virtuals as well?

 In CLUT modes, ovdi does not keep a separate palette, since such palettes
are global, i.e, a change in one palette affects the actual color
displayed, and in this case the opnvwk(), vs_color(), clsvwk() scheme will
work. However, I still think this is wrong.

 As far as I know, there is no support from the VDI's side to set a
palette on an 'application basis', that is, setting palette that will
affect all workstations opened by a process.

 What I can see from this, is that the virtual used to attribute the
resourcefile, is the virtual one must use to render the resource file to
screen, if using the palette in that resource file. I got around this
problem in my object library using color distance calculation when in 256
color LUT modes. I have plans to do something like that in XaAES as well,
which will make palette modifications not needed.

> that. I must have changed the driver color handling completely for this I
> must say....

 I dont understand.. please explain.


 Odd Skancke - ozk.atari.org - http://assemsoft.atari.org