Gena01.com Forum

Software Development => Win32Pad => Topic started by: Gena01 on May 05, 2003, 07:11:10 am



Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 05, 2003, 07:11:10 am
Known issues:
o Help file needs to be updated.
o Need to check the setup code. But it should be ok.
o Unicode support (double-byte) characters is NOT currently implemented. I might add this to a later version.

I have updated the version of NSIS used, maybe there is a way to clean up the setup script

Please report any issues, ideas, flames here.

Gena01





Title: Bugs in Win32Pad 1.3
Post by: Koala on May 05, 2003, 10:20:23 am
Only a small typo... should be "Print dialog"

x Fixed the settings in Pring dialog to print page ranges.


Other than that.....it works perfectly :)
We finally got the line numbers!! Hurray!

Could you kindly consider the addition to the types of filters
beside *.txt ? Keep up the good work !! ^_^


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 05, 2003, 11:16:00 am
Quote (Koala @ May 05 2003,11:20)
Only a small typo... should be "Print dialog"

x Fixed the settings in Pring dialog to print page ranges.


Other than that.....it works perfectly :)
We finally got the line numbers!! Hurray!

Could you kindly consider the addition to the types of filters
beside *.txt ? Keep up the good work !! ^_^

Heh, not enough sleep. :)

Gena01


Title: Bugs in Win32Pad 1.3
Post by: laserlight on May 06, 2003, 10:51:34 am
hehe, yeah, I would like to ask for association with the .php extension too.

Well, I dont think this is much of a bug, but when minimize to tray is used on a full screen instance of win32pad, on maximization it takes on the default size again.


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 06, 2003, 11:28:31 am
Quote (laserlight @ May 06 2003,11:51)
hehe, yeah, I would like to ask for association with the .php extension too.

Well, I dont think this is much of a bug, but when minimize to tray is used on a full screen instance of win32pad, on maximization it takes on the default size again.

Ah, yes... I see it.. will take a look at this when I get home.

Gena01


Title: Bugs in Win32Pad 1.3
Post by: Controller on May 08, 2003, 09:35:27 am
2 Bug:

1. Start Win32Pad, type any nonsense; Now press backspace to delete about half of that nonsense, and press undo ... and your document is empty!!!

2. When copying and pasting a new line, Win32pad does not make a line-break, ... It's maybe not a bug, but getting on my nerves :) . (Sometimes it even works, maybe it depends on a dll file or other software. Once it works, it works forever, but when reinstalling windows, it does not) (Please note that I'm using a tuned windows 95)


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 08, 2003, 09:55:05 am
Quote (Controller @ May 08 2003,10:35)
2 Bug:

1. Start Win32Pad, type any nonsense; Now press backspace to delete about half of that nonsense, and press undo ... and your document is empty!!!

2. When copying and pasting a new line, Win32pad does not make a line-break, ... It's maybe not a bug, but getting on my nerves :) . (Sometimes it even works, maybe it depends on a dll file or other software. Once it works, it works forever, but when reinstalling windows, it does not) (Please note that I'm using a tuned windows 95)

You might want to install new version of riched20.dll (since the one that comes with win95 is really old and buggy).

Gena01


Title: Bugs in Win32Pad 1.3
Post by: laserlight on May 08, 2003, 09:57:21 am
I'm running Win98 2nd ed., cant seem to reproduce the deletion bug.

As for the line break thing, never seen it before.
Do you mean that the multi-line text copied somehow doesnt have the 0x0d 0x0a characters (assuming windows)?

If it is only a single line, it is quite possible that you copied without those characters on your own.


Title: Bugs in Win32Pad 1.3
Post by: on May 09, 2003, 12:03:05 pm
Not a bug, but I really like the fact that you now get the message, "File has changed.  Reload?"

Now when I open a file twice, or when someone else is editing the same file as I am, I'll know it.

Great!

Had I thought that you would be able to implement that, I would have suggested it a long time ago.  (And I though VIM was the only editor to do something like that.)


Title: Bugs in Win32Pad 1.3
Post by: on May 10, 2003, 11:20:15 am
Thanks for your concern about the Double Byte characters. But I have found another strange bug. I don`t if you notice that the undo and url menu items have the same accelerator"R". What`s more, the url menu item is always disabled(grey). So would you please check it out?


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 12, 2003, 09:22:33 am
Quote (Guest @ May 10 2003,12:20)
Thanks for your concern about the Double Byte characters. But I have found another strange bug. I don`t if you notice that the undo and url menu items have the same accelerator"R". What`s more, the url menu item is always disabled(grey). So would you please check it out?

Hmm... thanks for pointing this out. I will resolve this in the next version.

Gena01


Title: Bugs in Win32Pad 1.3
Post by: on May 13, 2003, 10:29:53 am
Cursor cannot be seen with some background color


Title: Bugs in Win32Pad 1.3
Post by: on May 13, 2003, 10:31:24 am
Since you're giving it away for free, why not make it Open Source, and we can help you?


Title: Bugs in Win32Pad 1.3
Post by: MKairys on May 14, 2003, 08:11:58 am
In Win32Pad 1.2.2 Bugs was the following:

When the statusbar is disabled and I load a text that is longer than the window height, the vertical scrollbar does not appear.

You replied:

Posted: April 07 2003,21:43  

Thanks Wim,  for reporting this. I have managed to find the problem and fix it.. Will be fixed in the next release.

 
However I see in 1.3 that the problem is not entirely fixed. If the window is initially larger than the text and is resized smaller the scrollbar does not appear. It appears as soon as the window is resized larger.


Title: Bugs in Win32Pad 1.3
Post by: on May 14, 2003, 10:43:59 pm
There is a small bug with the reload from file feature.
If I make changes to a text file and save it, then open a new file in the same window (either by dragging or the file dialog). The reload file dialog pops up to ask me if I want to reload the file (the  file I've just saved and want to close). If I click on no, there is no problem and the new file loads, but if I click on yes (to reload the file being closed) I get the following error message Can't open file ""! The specified path is invalid.
One thing that might be effecting/creating this error is the following: I renamed the win32pad.exe to notepad.exe to fool windows into thinking that win32pad is notepad.

Other than this little problem, win32pad is looking good.


Title: Bugs in Win32Pad 1.3
Post by: laserlight on May 15, 2003, 06:18:06 am
This might just be a bug:
1. Open a file, do not edit it.
2. Attempt to open another file.
3. The message: "File has been changed. Reload?" appears.
4. Clicking yes makes the 1st file reload, only by clicking no does the 2nd file get loaded (which makes sense).

What does not make sense is why there is "File has been changed. Reload?" message in the first place.
If the 1st file was edited, a "save your changes" message does appear, but only after the reload query message.

I think that the intended effect would be not to have the reload message at all, and only keep the save query message if the file was edited.

EDIT:
hmm... now looking more closely at CK Watts's bug report, since loading a file by drag and drop is equivalent to opening the file by the menu interface, I'd say the problems are one and the same.


Title: Bugs in Win32Pad 1.3
Post by: on May 16, 2003, 11:24:33 am
Ok, I have been able to duplicate CK & laserlight's 'bugs'.

Does not seem to depend on the .exe name - notepad.exe & win32pad.exe both do the same thing.

If you select one of the "Recent files" this does not occur.

If you double-click a file this does not occur.

Seems like it only happens if you use the File-Open (Ctrl-O) dialog.


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 16, 2003, 01:09:15 pm
Quote (Guest @ May 16 2003,12:24)
Ok, I have been able to duplicate CK & laserlight's 'bugs'.

Does not seem to depend on the .exe name - notepad.exe & win32pad.exe both do the same thing.

If you select one of the "Recent files" this does not occur.

If you double-click a file this does not occur.

Seems like it only happens if you use the File-Open (Ctrl-O) dialog.

I have managed to replicate the bug on Win98. Thanks to laserlight for pointing that out. Somehow on Win2k it's fine.

I am currently investigating it.

Gena01


Title: Bugs in Win32Pad 1.3
Post by: on May 16, 2003, 02:49:14 pm
This may not a bug, but hope it works:
Input some quoted words like 'I','AM','A','STUDENT',
you can't hightlight the word you double-clicked on.



Thanks,


Title: Bugs in Win32Pad 1.3
Post by: on May 22, 2003, 08:03:31 am
Hi!
Thanks for this great program - I like it a lot.

However, since version 1.3 there seems to be a bug with the "save as.."-function.
When I open a textfile, go to File -> save as and enter a new filename I get the following error message:
"File has been deleted. Keep it in editor?"
If I select an existing file as the new filename I get the "file has changed. reload?"-Dialog.
Quite irritating.

I hope you can reproduce (and fix?) this bug. Thanks.


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 22, 2003, 08:43:22 am
Quote (Guest @ May 22 2003,09:03)
Hi!
Thanks for this great program - I like it a lot.

However, since version 1.3 there seems to be a bug with the "save as.."-function.
When I open a textfile, go to File -> save as and enter a new filename I get the following error message:
"File has been deleted. Keep it in editor?"
If I select an existing file as the new filename I get the "file has changed. reload?"-Dialog.
Quite irritating.

I hope you can reproduce (and fix?) this bug. Thanks.

I have managed to reproduce this bug, thanks to laserlight. It happens on win9x but not on win2k. I am working on a solution.

Gena01


Title: Bugs in Win32Pad 1.3
Post by: Gena01 on May 23, 2003, 10:35:37 am
Ok, I have spent some time yesterday night fixing the "File changed, reload message..." that was happening on windows98. I have a fix that seems to work, but I still need to do some more testing to see that I didn't break anything with the new code.


P.S. I have fixed some other reported issues like:
- Double clicking on the tray icon doesn't restore the window state  properly.
- I have finally fixed up the line number drawing code a bit. It's behaving much better now.
- I think that I finally fixed the problems with the borders and resizing and turning on/off toolbar/statusbar.

Gena01


Title: Bugs in Win32Pad 1.3
Post by: on May 23, 2003, 06:23:37 pm
How about making the line numbering a "toggle".  It would fit right in, right next to the WordWrap toggle.  Heck, I even devised an icon for it, #.  :)


Title: Bugs in Win32Pad 1.3
Post by: laserlight on May 24, 2003, 07:01:14 am
This has to do with selecting text that spans more than the current width of the instance, in my case full screen.

Using my mouse pointer to click and drag doesnt seem to allow me to go beyond the width of text editing area.
I would think that normal use would allow that.

EDIT:
actually, in retrospect this isnt really a bug, since it wasnt implied as a feature and there still is the selection bar while selection of the out of range text can be done especially with word wrap.