download filter updates all at once

if you're using the old style of downloading, you can just check them all and then download all at once. there is an option in 'options' that let's you pick this.

oh, you want to submit more than one at a time. sorry, i mis-read that.

no, i think you can only update one at a time. so, i'll shut up now and let the FF guys handle this. yes, it would be a good feature.

oh, ummm, the 'tools, updates' item is to update Filter Forge itself, not any given filters. this would be just a single action that would update filter forge with a new version of filter forge (currently version 1.006).

to get updated filters you use the normal download function and pick the item at the bottom.

You can shift-click to select more than one filter, if I remember correctly.

ssamm, sorry about not understanding what you were after. you can also do multiple updates from the normal download area. the last download item is updates and you can just click all of those and do them all at once. i never use the 'filter updates' thing.

Another proof that people don't read texts in user interfaces

lol, vlad. read? you've got to be kidding. 'we douwn need no steenking reading!' (sorry, mel brooks reference )

Quote
Kraellin wrote: ol, vlad. read? you've got to be kidding. 'we douwn need no steenking reading!'

That's what I've been telling the devs for years, but nobody believed me. I'm serious here, most people immediately jump to meaningful stuff (clickable / draggable / adjustable controls) and skip the texts.

vlad, i first noticed that devs were catching on to this back when i started seeing programs come with a 'quick start' method of using a program. you'd even see notices in the docs about 'if you just want to jump in without reading the manual, here's the quick docs'.

i tend to be one of those people. i jump in head first and only read when i cant figure something out by looking at it. but, i do eventually read, since there's always something i dont know. it's a bit of a trick getting to know a program sometimes. but, there are almost always certain things that are going to be familiar and certain things not so much. photoshop is a good example for me. i just bought it. i've used paint shop pro for years but never had photoshop. a lot of ps is familiar to me just because i've used psp, so why read about what you already know. but, ps is much more complex than psp, so there's going to be a lot of reading there if i want to get proficient with it.

there are still things i dont know about FF. i couldnt tell you what a specular map is or a normal map, but these mostly dont apply to how i use FF, so i dont worry about it too much. but i have read some of the wiki's, like the one where you pointed me too not too long ago regarding the 'mapping principle' of FF components.

when i study something, i want to know how to DO something. if i already know how to do it, why spend the time reading how to do it. where the gray area comes is when i dont know how to do something but try to figure it out with trial and error. now, that can get you into trouble. i've already run into this with photoshop. i assumed some things would be the same in ps as they are in psp. ah, the danger with assumptions. so, i've definitely got some reading to do there

so, you're always going to have those that jump in and DO and those that want to read the entire manual before they ever peek inside the engine or even before they install the program. the best method is probably a mix of those where you read the manual while you've got the program open and are DOING while you read about it.

we've heard for years now about 'intuitive programs' or 'intuitive interfaces'. and basically, all that means is, more doing and less reading or study. it's a good thing usually. FF is quite intuitive to me, but that somewhat comes from having a background in computers and computer interfaces. some things are just familiar. and having visual components to work with instead of code facilitates an ease of use also. we humans tend to be quite visual. you can explain something in text, but you can also explain it visually, often as not. the whole chinese written language is based on visual. it's an interesting way of writing.

you've probably also run into this with writing up docs yourself. it tends to be the last thing in the world a programmer wants to do and the last thing that gets done, if it's done at all. and i see here on the forums a request for more tutorials and docs or a video tutorial dvd. this isnt uncommon.

there are certain barriers to study. the public schools dont teach this because they dont understand what they are or how to handle them. but they do exist and can be overcome. so, it's always a bit of a trick getting folks to understand. guys like uberzev and CF&M jump into FF and start producing amazing filters. others jump in and have difficulty and bow out. so, what's the difference in the two types? how do you get joe blow, who has very little experience with computer programs and such to understand and use your program? one guy jumps in and goes 'this is amazing' and immediately starts producing, while another guy jumps in and goes 'this is crap; it makes no sense'. how do you turn that second guy into the first guy? it can be done.