:shipit:
but, bbl.
Its interaction with uniforms is weird and I can't really piece together the different parts
Is just binding them to the texture unit it was created in order with fine, and the user is responsible for setting the proper uniform?
Is that also how HLSL works?
I feel like the user shouldn't have to manage that though
It can be merged now then.
I hope it works :shipit:
:D
Any thoughts on #113?
My first idea is to add a special buffer storage type
Essentially the slice type for this becomes
(*refcount, *base, length)
And getting a real slice from this would borrow.
Destructor would decrease the refcount
@cmr but Rc<> can not be sent between tasks, no?
kvark @kvark didn't know GH closes referred issues automatically
Not sure we should actually do it -- @bjz?
not sure what it would look like
perhaps we should look to piston?
Due to the lack of associated types.
device uses types gldevice defines, gldevice implements traits device defines...
macro gods are kind to me today, I've got the shader link construction implemented:
struct Params {
b: gfx::BufferHandle,
x: int,
t: gfx::TextureHandle,
}
struct _ParamsLink {
b: ::gfx::BlockVarId,
x: ::gfx::UniformVarId,
t: ::gfx::TextureVarId,
}
#[automatically_derived]
impl ::gfx::ShaderParam<_ParamsLink> for Params {
fn create_link<S: ::gfx::ParameterSink>(__arg_0: &S) ->
Result<_ParamsLink, ::gfx::ParameterLinkError> {
::std::result::Ok(_ParamsLink{b: __arg_0.find_block("b").unwrap(),
x: __arg_0.find_uniform("x").unwrap(),
t: __arg_0.find_texture("t").unwrap(),})
}
}
It's not processing the result properly yet though
@kvark ooh neat
Just trying to find something to do
Can't write useful code with it until your shader parameter stuff is done :P
Or maybe I will try and set up a blog...