EyeBrowse
>>But when you delete the image file from DOS, how do you get rid of its twin?
I guess by hand. I played around with it a bit the other night and
created a bunch of thumbnails, then last night I cleaned out my image
directory. Now that I know to look for hidden files, I checked and had about
twenty thumbnails in the directory for files that no longer existed. The IPAS
now ignores these and the only way to loose them is to go in and delete these
hidden files by hand.
Aaron (if you catch this), Is there any way to have the routine, when
started, go in and compare existing thumbs to existing pics, then automatically
delete any stray thumbs? Or will this cause a noticable delay when using the
routine? I imagine that people who use it often can wind up with hundreds of
hidden stray thumbnails over time without even knowing it, unless they do ALL
of their image deleting in Eyebrowse. Also, how about including a set of 8-bit
images that can be read if the program notices the module it is run from is set
up for 8 bit? Would this speed up the initial start of the routine (I know it
would look better… at least the interface would, I know the thumbnails would
stay the same)? That's just an idea, but I run the meterials editor at 24 bit,
so I don't mind going into there to run Eyebrowse. Several IPAS routines I have
require the 3DE and KF to be set up for 8 bit, so I guess I really HAVE to go
into the Mat editor to run the browser at 24.
I've also noticed the routine randomly creating thumbnails in the
directory I have open. I'll just be sitting there doing nothing, and suddenly a
thumbnail or two will be created. Is this a known problem with the first
upload? Also, (I'm almost done, I promise) when I run the program from a
module set at 800x600x24 (my materials edit), any 800×600 image that is
displayed full screen takes an unusually long time to display (20 seconds,
versus a 756×480 or 640×480 which take 3 – 4 seconds). The same 800×600 image
displayed in Eyebrowse run from the 3d editor (set to 1024×768) takes only 5-6
seconds to display. Is this to be expected?
I find this a very useful utility and I do plan on getting the
registered version soon. 🙂 (I know this is adressed to you, Gary, but I
assume Aaron will see it.)
Thanx,
David