on_attach()

void MayaFlux::Buffers::SDFMeshProcessor::on_attach ( const std::shared_ptr< Buffer > &  )

overrideprotectedvirtual

Called when this processor is attached to a buffer.

Parameters

buffer

Buffer this processor is being attached to

Provides an opportunity for the processor to initialize buffer-specific state, allocate resources, or perform validation. With expanded processor capabilities, this method can also:

• Analyze Buffer Characteristics: Examine data type, size, and format requirements
• Select Optimal Backend: Choose the most appropriate processing backend for the buffer
• Initialize Hardware Resources: Set up GPU contexts, CUDA streams, or other acceleration
• Configure Processing Parameters: Adapt algorithm parameters to buffer characteristics
• Establish Processing Strategy: Determine whether to use sequential or parallel execution
• Validate Compatibility: Ensure the processor can handle the buffer's data type and format

Default implementation does nothing, but derived classes should override this method to leverage the full capabilities of the expanded processor architecture.

Reimplemented from MayaFlux::Buffers::BufferProcessor.

Definition at line 118 of file SDFMeshProcessor.cpp.

{
    ComputeProcessor::on_attach(buffer);
 
    auto vk_buf = std::dynamic_pointer_cast<VKBuffer>(buffer);
    if (!vk_buf) {
        MF_ERROR(Journal::Component::Buffers, Journal::Context::BufferProcessing,
            "SDFMeshProcessor requires a VKBuffer");
        return;
    }
 
    if (m_owns_buffers)
        rebuild_owned_buffers();
 
    bind_buffer("sdf_grid", m_grid_buf);
    bind_buffer("edge_table", m_edge_buf);
    bind_buffer("tri_table", m_tri_buf);
    bind_buffer("vertices", vk_buf);
    bind_buffer("counter", m_counter_buf);
}

References MayaFlux::Buffers::ShaderProcessor::bind_buffer(), MayaFlux::Journal::BufferProcessing, MayaFlux::Journal::Buffers, m_counter_buf, m_edge_buf, m_grid_buf, m_owns_buffers, m_tri_buf, MF_ERROR, MayaFlux::Buffers::BufferProcessor::on_attach(), and rebuild_owned_buffers().

Here is the call graph for this function: