ProScan Quick Fix

IdleMonitor

Member
Premium Subscriber
Joined
Feb 17, 2005
Messages
3,314
Reaction score
445
Location
The Ottawa Valley - Eastern Ontario
So I've had this problem now for I don't know how long now, but too long. Whenever I close down the ProScan program many times, when I go to open up the next time, doesn't matter if I've shut down the computer or whatnot, when I open it back up, not all the windows will open up. The 3 open windows to open and connect are the History logging window, Favourites Editor window and the virtual scanner window.

So this quick fix does work. Which you edit in the config file. Copy this into the config file, save and restart program. Supposed to work right away. It has, but doesn't all the time.

[WINDOW STATE]=
[WINDOW BOUNDS]=
[WINDOW LOCATION 1]=
[WINDOW LOCATION 2]=
[WINDOW LOCATION 3]=

So that's all fine an such, however for whatever reason recently, every single time almost that I shut down, reboot, unplug usb, uninstall, reboot, reinstall etc....I have to do the fix. However, even that won't work right away. It will open as I want it, but only have saved it in that position, but I can't reconnect right away. I have to do this whole process multiple times before I can open it up and have it connect right away with all windows in the correct position. Why?

I know the quick fix edit works, but why not right away like it should. Why do I have to keep doing all this after having completely shut down, and restart fresh.

This last time, took me about a half hour before it actually worked upon opening it up and in position that it connected right away.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,243
Reaction score
4,573
Location
Ontario, Calif.
I know the quick fix edit works, but why not right away like it should. Why do I have to keep doing all this after having completely shut down, and restart fresh.

I don't know why but if you had sent me a bug report via an email, I would have taken a look at it.

Send me a bug report and attach the proscan.cfg file. Edit out any login credentials first.

Bug Reporting

If you discover a bug, send an email to support@proscan.org. The advantage of email is so I can ask questions and send you production quality files with additional testing to help fix the bug. The person reporting the bug will get the fix sooner than waiting for the next release. Put "bug" in the Subject line. Bug Reports received via email in this format are assigned the highest priority.

Example:

Product (ProScan, Free Client, or RadioFeed):
Version:
Scanner type:
Windows version:
Options pertaining to the bug: Describe in detail what the bug is doing or not doing:
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,243
Reaction score
4,573
Location
Ontario, Calif.
What's the point of this forum then if everytime i ask about this or anything else for that matter im told to send a bug report?

Isn't this forum for asking about stuff like this?
This doesn't seem like a simple issue, I don't know what's going on. I don't even know what type of scanner, ProScan version, and windows you are referring to.
Email is the most efficient way to resolve bugs. I usually send out test files to see what the problem is then I send out a final version that has the fix.
 

IdleMonitor

Member
Premium Subscriber
Joined
Feb 17, 2005
Messages
3,314
Reaction score
445
Location
The Ottawa Valley - Eastern Ontario
This doesn't seem like a simple issue, I don't know what's going on. I don't even know what type of scanner, ProScan version, and windows you are referring to.
Email is the most efficient way to resolve bugs. I usually send out test files to see what the problem is then I send out a final version that has the fix.
You should receive the bug report via email very shortly.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,243
Reaction score
4,573
Location
Ontario, Calif.
You should receive the bug report via email very shortly.
Thank you.

{edit} I may take a quick look at the proscan.cfg file during the week to see if a work around is possible. I won't be able to send a test file as I'm going to start on the SDS150 support Tuesday.
 
Last edited:
Top