[eq-dev] Missing EQ_EXPORTs in FrameBufferObject and Texture

[m0bl0]

Hello,

all the member functions of eq::FrameBufferObject and eq::Texture are
missing the EQ_EXPORT declarations. I guess none of you use Windows
regularly? ;P

Thanks,
Marc
--
View this message in context: http://n2.nabble.com/Missing-EQ-EXPORTs-in-FrameBufferObject-and-Texture-tp3596623p3596623.html
Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.

_______________________________________________
eq-dev mailing list
eq-...@equalizergraphics.com
http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com

[Stefan Eilemann]

On Mon, Sep 7, 2009 at 12:58 PM, m0bl0 (via
Nabble)<[hidden email]> wrote:

> all the member functions of eq::FrameBufferObject and eq::Texture are
> missing the EQ_EXPORT declarations. I guess none of you use Windows
> regularly?

Not quite. We use Windows quite regularly, but these classes where
used only internally so far.

The eq and eq::net APIs are not yet fully defined yet, they are only
'official' when they are being used by one of the examples.

The Texture and FBO classes are relatively new, and the contract of
certain methods is not yet well defined. Nevertheless I added the
exports I thought useful and tried to improve the documentation
somewhat. They are still not 'stable' and you might find certain
limitations and quirks with them. Rev 3340 is for you.


Cheers,

Stefan.

---

View this message in context: Re: [eq-dev] Missing EQ_EXPORTs in FrameBufferObject and Texture

[m0bl0]

Stefan Eilemann wrote:
>
> On Mon, Sep 7, 2009 at 12:58 PM, m0bl0 (via
> Nabble)<ml-user+2481...@n2.nabble.com> wrote:
>
> The eq and eq::net APIs are not yet fully defined yet, they are only
> 'official' when they are being used by one of the examples.
>
> The Texture and FBO classes are relatively new, and the contract of
> certain methods is not yet well defined. Nevertheless I added the
> exports I thought useful and tried to improve the documentation
> somewhat. They are still not 'stable' and you might find certain
> limitations and quirks with them. Rev 3340 is for you.
>

Okay, that goes a long way (and the better documentation is also
appreciated!), but I still have more wishes: I'd also like access to
FrameBufferObject's addColorTexture and getColorTextures functions (and, I
guess, getDepthTexture and getStencilTexture for consistency). The reason
is, I want to render something into an FBO (with two color textures) and
then use it as a texture in another pass.

Thanks,
Marc
--
View this message in context: http://n2.nabble.com/Missing-EQ-EXPORTs-in-FrameBufferObject-and-Texture-tp3596623p3597988.html

Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.

_______________________________________________

[Stefan Eilemann]

On Mon, Sep 7, 2009 at 5:22 PM, m0bl0<tr...@in.tum.de> wrote:

> I'd also like access to
> FrameBufferObject's addColorTexture

That's an oversight on my end, fixed.

> and getColorTextures functions (and, I
> guess, getDepthTexture and getStencilTexture for consistency).

These should be fine since they are inlined!?

Cheers,

Stefan.

[m0bl0]

Stefan Eilemann wrote:
>
> On Mon, Sep 7, 2009 at 5:22 PM, m0bl0<tr...@in.tum.de> wrote:
>
>> I'd also like access to
>> FrameBufferObject's addColorTexture
>
> That's an oversight on my end, fixed.
>
>

Okay, perfect!

Stefan Eilemann wrote:
>
>
>> and getColorTextures functions (and, I
>> guess, getDepthTexture and getStencilTexture for consistency).
>
> These should be fine since they are inlined!?
>
>

Ah, of course. Sorry.

Thanks again,
Marc

--
View this message in context: http://n2.nabble.com/Missing-EQ-EXPORTs-in-FrameBufferObject-and-Texture-tp3596623p3598223.html

Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.

_______________________________________________