LionHeart123 / pyscripter

Automatically exported from code.google.com/p/pyscripter
0 stars 0 forks source link

Opening empty files gives an error #632

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create an empty file
2. Drag and drop file into PyScripter window
3. Receive Error
4. ?????
5. Post bug report!

What is the expected output? What do you see instead?
I expected to open the empty file in pyscripter

What version of the product are you using? On what operating system?
2.5.3.0 x86 - Window XP

Original issue reported on code.google.com by aaron.l....@gmail.com on 27 Mar 2012 at 2:09

GoogleCodeExporter commented 9 years ago
Cannot reproduce here.  I have tried:
a) Open the file (File Open)
b) Drag&drop from Windows file explorer
c) Drag&drop from PyScripter's File explorer
d) Double-clicking from PyScripter's File explorer

In all cases it worked fine.

Original comment by pyscripter on 27 Mar 2012 at 2:42

GoogleCodeExporter commented 9 years ago
Hi,

Here is the error message I get: http://i.imgur.com/0VsjJ.png

This happens no matter how I open the empty file. D+D, Explorer, 
RightClick->Open etc etc.

Regards,

Original comment by aaron.l....@gmail.com on 12 Apr 2012 at 12:18

Attachments:

GoogleCodeExporter commented 9 years ago
Please see the following: 
https://github.com/rnapoles/Synedit-Port/blob/master/SynEditWordWrap.pas#L301

If you are using this library it seems that the Assertions made here are what's 
causing the error. How are you calling this function and is there a possibility 
that negative numbers would be passed to it? I'm behind corporate firewalls and 
can't SVN checkout your code. 

Also, can you start using GitHub?

Original comment by aaron.l....@gmail.com on 12 Apr 2012 at 12:27

GoogleCodeExporter commented 9 years ago
Issue 679 has been merged into this issue.

Original comment by pyscripter on 3 Aug 2012 at 11:11

GoogleCodeExporter commented 9 years ago
The error only occurs when word wrap is on.  This is why I could not replicated 
it.
Fixed in version control.  The fix will be available with the next version.
Thanks for your help.

Original comment by pyscripter on 3 Aug 2012 at 11:13

GoogleCodeExporter commented 9 years ago
Hi,

Thanks for getting back to me. Good to know it's fixed.

Original comment by aaron.l....@gmail.com on 5 Aug 2012 at 11:08

GoogleCodeExporter commented 9 years ago
Is there an anticipated release date for the next version?

Original comment by ryankdal...@gmail.com on 7 Aug 2012 at 9:17