Comments on: Default parameter saving in Shader Toy http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/ Fri, 23 Jul 2010 01:34:59 +0000 http://wordpress.org/?v=abc hourly 1 By: Nick http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-400 Nick Thu, 11 Feb 2010 00:34:36 +0000 http://blog.nickgravelyn.com/?p=1346#comment-400 I currently have a working regex that handles the situation (taking into account line breaks, arbitrary spacing, and attributes) to replace the default value. It works, but I have some other issue to work out; my float slider always sticks to the max value when I tweak it. I'm guessing some circular "my slider changes the shader which forces a recompile which sets the parameter which changes the slider" type of issue. Just more fun stuff to fix. :) I currently have a working regex that handles the situation (taking into account line breaks, arbitrary spacing, and attributes) to replace the default value. It works, but I have some other issue to work out; my float slider always sticks to the max value when I tweak it. I’m guessing some circular “my slider changes the shader which forces a recompile which sets the parameter which changes the slider” type of issue. Just more fun stuff to fix. :)

]]> By: CrappyCodingGuy http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-399 CrappyCodingGuy Wed, 10 Feb 2010 14:09:11 +0000 http://blog.nickgravelyn.com/?p=1346#comment-399 Hmmm - that was all nicely indented when I typed it :( Hmmm – that was all nicely indented when I typed it :(

]]> By: CrappyCodingGuy http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-398 CrappyCodingGuy Wed, 10 Feb 2010 14:08:01 +0000 http://blog.nickgravelyn.com/?p=1346#comment-398 I guess the parsing seems fairly straightforward to me... for each line in the input file for each defined variable if the line contains the variable if a semicolon trails directly after the variable replace the semicolon with the default value + ";" else if an "=" trails directly after the variable find the trailing semicolon replace everything between "=" and ";" with the default value write the line to the output file - this will either be the unedited or modified line if everything succeeds delete inputfile.old rename the input file to inputfile.old rename the output file to inputfile.fx I guess the parsing seems fairly straightforward to me…

for each line in the input file
for each defined variable
if the line contains the variable
if a semicolon trails directly after the variable
replace the semicolon with the default value + “;”
else if an “=” trails directly after the variable
find the trailing semicolon
replace everything between “=” and “;” with the default value

write the line to the output file – this will either be the unedited or modified line

if everything succeeds
delete inputfile.old
rename the input file to inputfile.old
rename the output file to inputfile.fx

]]> By: Nick http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-397 Nick Wed, 10 Feb 2010 02:51:05 +0000 http://blog.nickgravelyn.com/?p=1346#comment-397 I don't see how it's reinventing the wheel. My goal is to not require custom content pipelines or runtimes for something as logically trivial as a default parameter value. Something that could easily be hand coded in the file shouldn't need a whole suite of attributes and runtimes just to be able to set that default with UI. And I already do support range limits for my UI (at least my float one); I just use 'min' and 'max' instead of the DXSAS names. I could switch or support both if I got the desire. ;-) I don’t see how it’s reinventing the wheel. My goal is to not require custom content pipelines or runtimes for something as logically trivial as a default parameter value. Something that could easily be hand coded in the file shouldn’t need a whole suite of attributes and runtimes just to be able to set that default with UI.

And I already do support range limits for my UI (at least my float one); I just use ‘min’ and ‘max’ instead of the DXSAS names. I could switch or support both if I got the desire. ;-)

]]> By: Björn http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-396 Björn Wed, 10 Feb 2010 02:40:49 +0000 http://blog.nickgravelyn.com/?p=1346#comment-396 So, doing it properly (yep, that might be a tiny tad exaggerating :)) is overkill but reinventing the wheel in a limited way is not? Also, sooner or later you might want to have something like the range limits for your UI, and later some other stuff of the DXSAS thingy :) Find something else to write a parser for :) So, doing it properly (yep, that might be a tiny tad exaggerating :) ) is overkill but reinventing the wheel in a limited way is not? Also, sooner or later you might want to have something like the range limits for your UI, and later some other stuff of the DXSAS thingy :)

Find something else to write a parser for :)

]]> By: Nick http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-395 Nick Tue, 09 Feb 2010 21:31:21 +0000 http://blog.nickgravelyn.com/?p=1346#comment-395 It seems like that's just overkill. To require a whole content pipeline just for a single default value seems like someone's doing something wrong. I can understand the use for having varying parameter sets, but for something this simple, why is changing it in the effect text such a bad idea? Other than trying to figure out the best way to parse the text and fix it. :) It seems like that’s just overkill. To require a whole content pipeline just for a single default value seems like someone’s doing something wrong. I can understand the use for having varying parameter sets, but for something this simple, why is changing it in the effect text such a bad idea? Other than trying to figure out the best way to parse the text and fix it. :)

]]> By: Bjoern http://blog.nickgravelyn.com/2010/02/default-parameter-saving-in-shader-toy/comment-page-1/#comment-394 Bjoern Tue, 09 Feb 2010 20:59:27 +0000 http://blog.nickgravelyn.com/?p=1346#comment-394 I think it was Catalin who said to use DXSAS + a custom pipeline compiler to emit non-DXSAS effect files, which is probably the way I would do it, too. But then I started to ignore my own NIH feelings recently :) I think it was Catalin who said to use DXSAS + a custom pipeline compiler to emit non-DXSAS effect files, which is probably the way I would do it, too. But then I started to ignore my own NIH feelings recently :)

]]>