Won't open log file in use
Moderator: kfury77
Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
Please try to follow these guidelines. This will help to receive faster and more accurate response.
- Check the Support section of the corresponding product first. Chances are you will find your answer there;
- Do not create new topics for already reported problems. Add your comments to the existing topics instead;
- Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
- Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
- Include the version number of the software you are using;
- This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Won't open log file in use
I just noticed that WeBuilder won't open a log file that is in use by a program. I use ClipMate and it makes a log file with a TXT filename. WeBuilder gives me an error while trying to load it and won't open it. I can open this file in EditPlus fine. Is this by design?
-
Karlis
- Site Admin
- Posts: 3605
- Joined: Mon Jul 15, 2002 5:24 pm
- Location: Riga, Latvia, Europe
- Contact:
Re: Won't open log file in use
I'm not sure about this situation, but by design WeBuilder looks at the lock state of the file and honors the state set by the other program. If the file is fully locked both for reading and writing, WeBuilder will not open it. I guess, it is possible not to honor the lick-state, but then again it is against the good style.
But as I do not have the ClipMate, I can not tell you for sure.
But as I do not have the ClipMate, I can not tell you for sure.
Re: Won't open log file in use
Wouldn't a message stating the file is locked or in use by another program be better for an error message then? Or maybe opening it in read-only mode?