Comments on: Visual Studio shader syntax highlighting part 2

By: Sam

Sam — Thu, 04 May 2017 00:59:48 +0000

Thanks for your bug report. It sounds like there’s a conflict with Nsight for some reason. I’ve added your report as an issue over here https://github.com/samizzo/nshader/issues/14. If you have any further info please post it there. I’ll try to find some time to look into it.

By: StanleyW

StanleyW — Wed, 03 May 2017 15:52:36 +0000

Hello!

there are some problems.

I have Visual Studio 2015 (with Nsight) and Visual Studio 2017. NShader just working on Visual Studio 2017. When using Visual Studio 2015 (with Nsight) to open the GLSL file, it’s just a normal text editor.

But on my other computer only Visual Studio 2015 (with Nsight), NShader can work.

So I think it’s not Nsight’s problem, right?
And how can I solve this problem?

By: Sam

Sam — Mon, 01 May 2017 11:15:38 +0000

Thanks! Some people have had some problems, but they’ve been hard to reproduce, so it’s great to hear it’s working for most people in 2017!

By: OpenGl

OpenGl — Mon, 01 May 2017 08:07:50 +0000

Works without any problems in VS2017 Community Edition.
Thanks

By: Alex

Alex — Wed, 23 Nov 2016 15:45:22 +0000

Hey,

It seems to work in Visual Studio 2017 as well :).

Thank you very much for this, @Sam!!

By: 8Observer8

8Observer8 — Wed, 07 Sep 2016 05:35:19 +0000

It will work for highlighting but I’m not sure that Ctrl+K, Ctrl+D will work corrently for html files.

May be it will usefull for somebody who want to use WebGL shader from files:

var VSHADER_SOURCE = null;
var FSHADER_SOURCE = null;

function main()
{
// …

readShaderFile(gl, ‘vShader.glsl’, ‘v’);
readShaderFile(gl, ‘fShader.glsl’, ‘f’);
}

function readShaderFile(gl, fileName, shader)
{
var request = new XMLHttpRequest();

request.onreadystatechange = function ()
{
if (request.readyState === 4 && request.status !== 404)
{
onReadShader(gl, request.responseText, shader);
}
}

request.open(‘GET’, fileName, true);
request.send();
}

function onReadShader(gl, fileString, shader)
{
if (shader == ‘v’)
{
VSHADER_SOURCE = fileString;
}
else if(shader == ‘f’)
{
FSHADER_SOURCE = fileString;
}

if (VSHADER_SOURCE != null && FSHADER_SOURCE != null)
{
start(gl);
}
}

function start(gl)
{
// Initialize the shaders
if (!initShaders(gl, VSHADER_SOURCE, FSHADER_SOURCE))
{
console.log(“Failed to initialize the shaders”);
return;
}
// …
}

By: Sam

Sam — Wed, 07 Sep 2016 05:21:19 +0000

Ahh I see! That’s a bit more complicated but I think it might work if you associate NShader with the file extension of your html file. But it would then apply the syntax highlighting to the entire file.

By: 8Observer8

8Observer8 — Wed, 07 Sep 2016 05:19:41 +0000

> Sorry I’m not exactly sure what you want to do.

It is WebGL. Please, see this link: https://msdn.microsoft.com/en-us/library/windows/apps/dn457645.aspx

But now I use file lile .glsl. and it not actual for me. I can use your tools.

By: Sam

Sam — Wed, 07 Sep 2016 05:18:49 +0000

Thanks! Unfortunately I can’t add those options because at the moment NShader doesn’t do any code completion or any of that stuff for formatting. That’s why I suggested HLSL Tools for Visual Studio. That plugin has those features.

By: 8Observer8

8Observer8 — Wed, 07 Sep 2016 05:12:15 +0000

It is very nice tool. I use shader files now (not in scripts tags)

Please, add two checkboxes to Options -> Formatting -> “New Lines”:
- “Place open brace on new line for functions and structures”
- “Place open brace on new line for control blocks”

How it is made for JavaScript. Thank you.

I found mistake. Please press Ctrl+K, Ctrl+D in .glsl file. You will see new line for every pressing.