Author Topic: Beta Testers For ScreenshotCaptor? (Read 64160 times)

mouser · « **Reply #25 on:** May 13, 2005, 10:20 PM »

thanks jef, i'll get it fixed, i just have to try to figure out a way to reproduce the bug here - you're not the only one getting this behavior.

--

new version up (won't help jeff's problem).
changes:
you can now set default image format to jpg,gif,png,tif (comments are saved in all now)
compression slider
sound is optional
statusbar now lists resolution and filesize of images as you view

--

new screens:

mouser · « **Reply #26 on:** May 14, 2005, 01:04 AM »

v 1.00.15 is up, better menu organization, cute new dropshadow shadow feature.

tenseiken · « **Reply #27 on:** May 14, 2005, 02:27 AM »

Slick shadow feature. You may want to consider breaking up the preferences panel--it has a ton of options. Maybe you could group them into two sections of related options?

mouser · « **Reply #28 on:** May 14, 2005, 02:31 AM »

yeah i should probably use tabs, as i have before.

who knew it was going to grow into so many options....

mouser · « **Reply #29 on:** May 14, 2005, 05:44 AM »

ok the prtsrc hook problem should be fixed now.

i just have to fix the problem causing crash on some machines..

nudone · « **Reply #30 on:** May 14, 2005, 07:51 AM »

yep, printscreen key functions now work fine on mine.

mouser · « **Reply #31 on:** May 15, 2005, 01:22 AM »

1.00.18 now up.

known problem: png files do not store comments

all other file formats do.

not too much changed on outside of this version, but the internal mechanisms for detecting file changes outside of app are completely redone, hopefully will work better with external graphics editors now.

can those who were experiencing that access fault error on startup tell me if it still happens or if its fixed now?

JeffK · « **Reply #32 on:** May 15, 2005, 01:27 AM »

Still happening, mouser - this is the message on my machine.

Access violation at address 004056BE in module 'ScreenshotCaptor.exe'. Read of address 00000330

mouser · « **Reply #33 on:** May 15, 2005, 02:10 AM »

thanks jeff..
damn i thought for sure that would fix it..
ok, i will keep looking for the problem. probably something super simple.

mouser · « **Reply #34 on:** May 15, 2005, 02:26 PM »

version 1.00.19 now up - jeffk can you test and see if it cures the problem?

tenseiken · « **Reply #35 on:** May 15, 2005, 02:38 PM »

I'm not getting any error messages, but it would appear that it's having trouble reading the .ini file on my machine. When I run it while the .ini file is present, it hangs and the tray icon never appears. However, when I delete the .ini file and run it, it works fine. This is 1.00.19, by the way.

mouser · « **Reply #36 on:** May 15, 2005, 02:41 PM »

can you check to see if its not just a really slow startup with the ini file?
give it 5 or 10 seconds - just so i know if its really a hang or a dif issue.

JeffK · « **Reply #37 on:** May 15, 2005, 04:21 PM »

version 1.00.19 now up - jeffk can you test and see if it cures the problem?
-mouser (May 15, 2005, 02:26 PM)

I hereby declare it fixed. Stand up and take a bow, mouser!

Thank you,

Jeff

mouser · « **Reply #38 on:** May 15, 2005, 04:46 PM »

great to hear that that is fixed, though it created this startup delay.

im going to try one more fix compromise and see if that solves it..

JeffK · « **Reply #39 on:** May 15, 2005, 04:49 PM »

On my setup it only takes 2-3 seconds to startup. In fact, if I close it down and restart it, it takes less than 1 sec.

Jeff

mouser · « **Reply #40 on:** May 15, 2005, 05:06 PM »

yeah works for me too without startup issues, but with one experimental version i did notice a strange bug with like a 10 second startup.. and im wondering if that wasnt the problem tenseiken was experiencing.. i have something i can try to fix it..

tenseiken · « **Reply #41 on:** May 15, 2005, 09:38 PM »

It's not just a slow startup... I just gave it a couple minutes to run. No luck.

mouser · « **Reply #42 on:** May 15, 2005, 09:48 PM »

how strange...
so if you delete the ini then it runs, but after you exit and restart, it hangs (without even showing icon), is that right?
but the other versions did work..

really strange. i will try to fix.
if you have some time it might be nice for you to play with the .ini file a bit and see if changing anything or deleting an entry fixes it.
in particular, try changing the FolderPathEdit.Text entry or deleting it.

tenseiken · « **Reply #43 on:** May 16, 2005, 02:24 AM »

Now that you mention it, it may not just be this version. I think I remember having to delete the .ini file while installing a new version a time or two. At the time, I assumed it was the new version not reading the old .ini file properly--I don't think I ever actually closed and re-ran the program without installing a new version until now.

I went through all the preference changes I made one by one to see which one broke it, and after doing so, it's still running. I wonder if it's the combination of changes I was making all at once. Sorry I can't be more helpful, but if you have any other ideas, I'll be happy to test them. I've taken a few screenshots, and I've noticed that for some reason, it started placing them in the folder above the one I specified, and after that, it broke down and stopped running. Removing the entry you mentioned did not help at this point.

mouser · « **Reply #44 on:** May 16, 2005, 03:00 AM »

i think these bugs are all related to the same problem,
they sound like a problem i thought i had fixed, with the program getting confused about the directory it is in,
i just wish i knew a way to reproduce it. any think strange about your directory structure that might cause the problem?

question, if you try browsing arround using the .. entry
ie just navigate around directories and dont try capturing antyhing
and see if the program confuses itself and gets lost, etc.

tenseiken · « **Reply #45 on:** May 16, 2005, 11:55 AM »

I've been able to reproduce the error without changing any settings. There seems to be a difference between exiting with the system tray and exiting with File->Exit. Still, it almost seems random. Sometimes it will work and sometimes it won't--I haven't been able to distinguish a pattern As for it getting confused about the directories, I haven't the slightest clue. I don't install 3rd party programs onto my system drive and my screenshots aren't on the 3rd party or the system drive. I doubt that is what's causing it though. They're all NTFS, if that makes any difference.

mouser · « **Reply #46 on:** May 17, 2005, 05:21 AM »

well i don't hold much help of this latest version fixing it but it's worth a try.

jeffk, this version may bring back your crashing bug so please try as well if you dont mind.

would it be easier for you guys if i just uploaded the main app exe? or do you prefer the setup program?

[link out of date]

once i get this bug fixes i can start polishing the program.

btw - i did use this program for the email review, and it did help me

JeffK · « **Reply #47 on:** May 17, 2005, 06:10 AM »

No, it didn't bring back the crashing behaviour. Appears to start quickly and work normally.

Thanks,

jeff

tenseiken · « **Reply #48 on:** May 17, 2005, 11:02 AM »

Now it works sometimes and sometimes it doesn't... I wonder if this is just a problem on my end. It seems like it's more likely to work properly after killing the process with taskmgr than if I exit it from the program.

mouser · « **Reply #49 on:** May 17, 2005, 11:46 AM »

you know, the program does have code to prevent it from opening multiple copies - perhaps that is getting confused;
let me upload a version with that turned off, and see if that doesn't fix the problem.