Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
...and as regards the "history/memory", do you mean referring to a particular line, like "line 3"? ...No, what I meant by 'history' is that a session would automatically be saved upon exit. I do see that you already have a "Save" function, which is nice, but I often don't think I'll need to re-visit a calculation when, later, I then do. For example yesterday I calculate 2+2, but don't think I need to save it. Then, sure enough, today I run in to 2+2 again, or worse, I can't even remember what the two numbers were that I had needed to sum. It would be nice if OC saved those in memory, then I could just activate the "Show history" command and it would show me. I guess there'd need to be an option to tell OC how many days to keep history items before purging them. Otherwise you'd get hundreds accumulated, slowing down performance. Also, (my thinking is) as long as the data was saved at exit, it could be pulled off of disk by OC when needed. Therefore it wouldn't need to affect startup performance (i.e. it wouldn't get automatically loaded into RAM).-Twinbee (April 08, 2012, 10:29 AM)
I'm not sure if the 'Saturation' sliders work as expected though. They seem to change the tint somewhat, rather than "saturation" per se.... ..., they perform blending and distortion because they cannot map the pixels 1:1 (different perspective projections, different brightness and contrast on different photos). If you actually feed them "ideal" pictures where 1:1 mapping is possible, would they still distort the result? My naive guess would be that they won't.This is also what I was thinking... Especially the Microsoft ICE one. It lets you choose how flat the image should be. I would imagine there could be problems though, if different sub-components don't have enough visual info (such as a near empty space in the ocean).-vlastimil (March 20, 2012, 02:07 PM)
