changelog:
- implemented hpu.fill() function *same as the hologram api, but for multiholo*
- implemented hpudraw.vertex(point1,point2,point3,value) -- with points a table {x=,y=,z=}
- implemented some more vector math functions in the vector module.
sorry no pictures of the new features, can't find out how to add a picture in 0.02MB :-/
EDIT: cause I don't want to post twice in a row:
version 0.3 is ready!!
changelog:
==Changes:
- hpu.bind(hologramProxy,x,y,z) now can be called with an additional colorPalet table.
hpu.bind(hologramProxy,x,y,z,palette) where palette would be something like {1,3,5} -> this means the colorPalet index 1,3,5 will work for this hologram.
on binding it will overwrite the hpu.palette colors with the hologramProxy's already configured colors.
- hpu.get(x,y,z) will now return a table of found voxels -> this so that if multiple holograms act on the same x,y,z position you get all there results back.
==bug fixes
- fixed a memory leaky bug where running the same program where hpu.bind was used on a already bound hpu would register it a second time.
==Additions:
- hpu.setPaletteColor(index,color) this way you can set a color for an index, it also will push this color to all the bound holograms that are registered for this indexed color.
- hpu.getPaletteColor(index) just to get the color configured in the hpu global palette
- hpu.initColors() if you have changed the colors directly on the hologramproxy, but want to reset them to the configured hpu.palette, this also will be called on a setPaletteColor of the hpu.
- hpu.setModeMultiColor(boolean) this will make it so that any hologram will first try to unset the voxel on the specific 3dpoint on hpu.set, this makes that only holograms with the chosen color will act, and no overlap will be visible on the hologram. (if you want to mix voxels and so make multiple colors just don't enable this and you can mix them to make colors by using 2 different voxels on the same position.)
- hpu.version => just for organising my changelogs