| Burt |
I was optimizing a filter and wonder if the scripting would allow creating a component that you could run to query the components in a filter for certain values (based on some of the optimzation suggestions I am reading now). For example "Find all [type of component] Noise with Roughness AND OR Detail > 0" and maybe click to jump to these components or set multiple values or even just show a list "You have 4 Noise components with Detail > 0"
In a complex filter finding each and every setting takes time so maybe this would be useful, just plugin it in when you need it and remove after done. |
|
| Posted: February 27, 2013 7:15 pm | ||
| Burt |
Actually I see that a search of the XML file will give me the info so I can probably search and edit that there if needed. Need a delete button on these forums, too many of my rambling ideas on here.
|
|
| Posted: February 28, 2013 12:18 pm | ||
xirja
 |
Right. That all the filters are stored as XML files is very helpful, you can read the contents with a text editor and program custom apps (outside of FF) to count components/controls, rewrite them, etc. Because of this, I already have control locks and named presets.
 Thank you Filter Forge, thank you Mathematica!
Being able to delete posts would be nice, but I'm thinking its more appropriate in the case of people who post more than 300 posts/month. 
Especially with the new grouping feature, its going to become even more needed for some way to find something many levels nested. Easy to change values using the XML editing method, but if you wanted to replace a component?  _____________________________________________________
http://web.archive.org/web/2021062908...rjadesign/ _____________________________________________________ |
|
| Posted: February 28, 2013 2:43 pm | ||
| Burt |
Cool. I actually found a nice free XML editor by Microsoft (not sure if some else has something better but here it is -sorry if this is off topic)
*Darn missing delete key!*
Actually I edited a file to try to change a component name and now FF does not recognize it so I removed the link. It didn't like something. I guess the thing with mucking with XML direct is you don't have any logic to restrict the changes to ranges accepted by FF. You'd need either a seperate 'rules' file so that people making external components can query acceptable ranges for each component or a checkbox for a 'verbose mode' to export the xml with non-rendering comment blocks for each component ie "ABC Component: Height: acceptable range 0-100" - but just thinking outloud as usual. |
|
| Posted: February 28, 2013 3:28 pm | ||
Join Our Community!
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,533 Posts
+38 new in 30 days!
15,348 Topics
+73 new in year!
Online Users Last minute:
17 unregistered users.
Recent Forum Posts:
- Manson Grudge Border by Jaret by Minko
8 hours ago - Kaleidoscopic Variations Vol. 2 by jhantares by jhantares
September 10, 2025 - Polygonal Images Set by Ramlyn by westdale
September 10, 2025 - FF Killing Resolution by SpaceRay
September 9, 2025 - Geometry Spinner by Rachel Duim by Rachel Duim
September 6, 2025 - Channel Glitch by Martin Naumann by SpaceRay
August 31, 2025 - Circuit Glitch by Martin Naumann by SpaceRay
August 31, 2025 - Groovy Rays by Ramlyn by Ramlyn
August 31, 2025 - Is Ultraforge dead? by dpankros
August 30, 2025 - Component Instances by AussieDecalf
August 27, 2025 - Hyperbolic Tiling Challenge by AussieDecalf
August 27, 2025 - Chaos Fields by SpaceRay
August 27, 2025
