From 2f33f35791cf509e188395b5f80133b0dc34b5af Mon Sep 17 00:00:00 2001 From: Elie Michel Date: Sun, 24 Nov 2024 15:54:05 +0100 Subject: [PATCH 1/2] Fix broken link in 09-reflection.md --- docs/user-guide/09-reflection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/09-reflection.md b/docs/user-guide/09-reflection.md index 0c93112123..ff874fb5fd 100644 --- a/docs/user-guide/09-reflection.md +++ b/docs/user-guide/09-reflection.md @@ -13,7 +13,7 @@ The Slang API allows layout to be queried on any program object represented by a slang::ProgramLayout* layout = program->getLayout(); ``` -Please see the [Compiling Code with Slang](/user-guide/compiling) section on creating program objects. +Please see the [Compiling Code with Slang](compiling) section on creating program objects. Note that just as with output code, the reflection object (and all other objects queried from it) is guaranteed to live as long as the request is alive, but no longer. Unlike the other data, there is no easy way to save the reflection data for later user (we do not currently implement serialization for reflection data). @@ -224,4 +224,4 @@ unsigned int attribCount = funcReflection->getUserAttributeCount(); slang::UserAttribute* attrib = funcReflection->getUserAttributeByIndex(0); const char* attribName = attrib->getName(); -``` \ No newline at end of file +``` From 3be64968480de2faeba8b4d37f2aec7deab33378 Mon Sep 17 00:00:00 2001 From: Elie Michel Date: Sun, 24 Nov 2024 17:17:29 +0100 Subject: [PATCH 2/2] Fix another link on 08-compiling.md --- docs/user-guide/08-compiling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/08-compiling.md b/docs/user-guide/08-compiling.md index 6f60ef6f8c..23a33d9147 100644 --- a/docs/user-guide/08-compiling.md +++ b/docs/user-guide/08-compiling.md @@ -829,7 +829,7 @@ The details of how Slang computes layout, what guarantees it makes, and how to i Because the layout computed for shader parameters may depend on the compilation target, the `getLayout()` method actually takes a `targetIndex` parameter that is the zero-based index of the target for which layout information is being queried. This parameter defaults to zero as a convenience for the common case where applications use only a single compilation target at runtime. -See [Using the Reflection API] chapter for more details on the reflection API. +See [Using the Reflection API](reflection) chapter for more details on the reflection API. ### Linking