Forum : Ride IDE
Post Information | Post |
---|---|
June 21, 2010 - 9:46am
|
Hi, 1. Copy & paste a function or line of code The solution is to close the file and then reopen. Sadly this occurs too often (read several times per hour). No other occurrences in other programs so I'm leaning towards a bug in Ride7 editor. I'm using Has anyone had this issue or a permanent solution? |
Hi MartinJ,
Is this happening during a compilation session or at anytime?
Is the file open in another application?
The problem you are reporting happens when a file is modified and compiled at the same time.
Best regards,
Behnaz
Hi Behnaz
>Hi MartinJ,
>I this happening during a compilation session or at anytime?
The problem occurs during editing. If I start the program from scratch Ride automatically loads the previous project. I then start to work and the bug occurs within a short time.
>Is the file open in another application?
No
>The problem you are reporting happens when a file is modified and compiled at the same time.
I'm not sure that it is necessary to compile in order to produce the bug. It might be that an old compilation session is active but cannot see any active process or file handle after closing the editor.
>Best regards,
>Behnaz
I've experienced this bug in the previous edition of Ride7 7.28.10.075 as well.
A college is using winxp sp3 but have not experienced the bug as frequently, only on a rare occasion.
Thanks for helping me out.
//Martin
Ride7 editor has an open issue regarding the sharing of editor files with other applications. This should be corrected in the coming versions of the software.
In meanwhile to help you solve this inconvenience, my guess is that when you are saving your files, another application (antivirus or something else) is automatically activated ending up with this sharing problem.
Best regards,
Behnaz
Hi,
I'll try to disable the antivirus from scanning the source files. I'll report back if this solves the issue.
Thanks for the help! Looking forward to the next release.
//Martin
Hi again,
I disabled the virus-scan for source code files and it seems to have helped solve the problem temporarily.
I'm using Nod32 Antivirus 4.2.40.18 Business Edition and I'm using real-time threat sense. Seems like Nod32 scanned my source files upon saving thus triggering the bug.
Thanks again Behnaz, Your help was much appreciated!
Martin