NexPad 0.6

[Veedems Veteran]

Ok guys, let me know what you want me to do. 0.4 BETA is ready to ship with the exception of that one drag and drop bug. I can either keep waiting until the December BETA of visual Basic express is released or I can simply disable the drag and drop event on the text box, for now. You would still be able to drag and drop files simply by dropping them on any other part of the window except for the text box. Which do you want?

[war]

I would perfer to wait I guess as its working perfectly as it is.

But I would still help test either way. ;)

[Veedems Veteran]

Well, I guess I'l lwait then and hope the bug is fixable in the next release of the IDE.

[j.r.l.]

Whats IDE? Isnt an hd connector?

[Veedems Veteran]

Whats IDE? Isnt an hd connector?

584999740[/snapback]

Integrated Development Environment

[j.r.l.]

ohh funny

[jtchange]

nice program, I like (Y)

[Veedems Veteran]

nice program, I like  (Y)

584999885[/snapback]

Thank you. Once I get that bug sorted out (hopefully when the next 2005 express is released), I will get 0.4 out the door. Let me tell you, it's a lot more complete and I have gotten quite a few bugs fixed. I would post the changelog, but I want it to be a surprise lol.

[war]

lol AresXP

Remember google is your friend. :p

First few results btw. :blink:

[Keito]

I can't wait till 0.4 gets released... NexPad is something I actually use daily and instead of notepad :yes:

[Dotdot]

I can't wait till 0.4 gets released... NexPad is something I actually use daily and instead of notepad :yes:

585001301[/snapback]

Amen :)

[j.r.l.]

lol AresXP

Remember google is your friend. :p

First few results btw.  :blink:

585001053[/snapback]

I'm a Google pro :blush:

[war]

Well guess its dead, afterall? :(

[insanekiwi]

Whats IDE? Isnt an hd connector?

584999740[/snapback]

post of the day for me :rofl:

[Veedems Veteran]

Well guess its dead, afterall? :(

585103866[/snapback]

It's not dead at all, just waiting on the December release of VB .Net 2005 so I can hopefully figure out how to fix that one bug. I had asked a while back and no one answered. I can release 0.4 today, if you want, but I will have to disable drag and dropping of files, from explorer, into the area where you type text. You will still be able to drop the files anywhere else on the form and have them open in NexPad, but dropping files into the textbox where you type, right now, leaves a link to the file that I do not want appearing. This behavior is new to the 2.0 framework.

[CJC]

Just a quick reproducable bug notice, not sure if this has been posted yet:

Open nexpad.exe, then hit the X (almost top right) to close the inner document window, but not the program. Then try to open the edit menu. It crashes the program and I get this error message. Anyone else get this?

I'm running Nexpad 0.3 Beta on XP SP2

[Veedems Veteran]

Fixed in 0.4. Thanks anyway.

[CJC]

Fixed in 0.4. Thanks anyway.

585107401[/snapback]

Not a problem :happy:

[war]

Yeap I saw that too a few pages back.

https://www.neowin.net/forum/index.php?show...#entry584905039

Well ok it was to just get some attention to the thread anyways. ;)

[Veedems Veteran]

So you guys know, I will most likely wind up disablign dragging and dropping into the text area and only keep it enabled in the main window controls (such as the tab bar) and release 0.4 soon. I want to clean up some messy code, but, other than that, it's been ready for way too long and I need it released so I can take in people's reactions and see where I should go with the project next.

[Veedems Veteran]

Ok, either today or tomorrow I will finally get 0.4 out the door.

On a side note, I didn't get single instance in, yet, but as VS 2005 shapes up and some more documentation comes out, it may be easier than ever. Just hang in there, please.

[Veedems Veteran]

NexPad 0.4 is finally released. Please note, NexPad 0.4 now requires the Microsoft .Net Framework 2.0. Here is the changelog:

-------

v 0.4

-------

Released 01/04/2005

- Ported to .Net 2.0

- New icon

- Added 'highlight' option to find bar

- Added ability to middle click tab to close it

- Added rudimentary "previous" searching (will refine code at a later time)

- Added "Minimize to tray" option

- Added print preview capability

- Temporarily disabled drag & drop into text area. Still works anywhere else

- Refined behavior of pad that is selected after one pad is closed

- Fixed: Possible crash when selecting edit menu directly after closing a tab

- Fixed: Text formatting not saved properly for other apps to read

- Fixed: Crash when selecting edit menu with no pads open

- Fixed: Newly opened pads may not be sized correctly

- Fixed: Nonapplicable File menu options not disabled when no pads exist

- Fixed: Nonapplicable Pads menu options not disabled when no pads exist

- Fixed: Nonapplicable Format menu options not disabled when no pads exist

- Fixed: Attempting to find or replace text, with no open pads, would crash NexPad

- Fixed: Undoing all changes would still result in a "save prompt" when closing pad

- Fixed: Drag and dropping a file from explorer, with no open pads, would crash NexPad

- Fixed: Current line indicator was 1 off

- Fixed: Small graphical errors with tabs when status bar enabled (top of tabs cut off)

- Fixed: If file load, at startup, fails, a blank pad would not be opened as planned

- Cleanup: Removed nonfunctional, leftover code (extra if statements)

- Cleanup: Recoded much of the file load and pad creation functions

- Cleanup: Removed useless printDocument

Please check the first post of this thread for a download link.

new updated screenie:

[Menge]

so, you ported this to .Net 2.0 and now require us to use a Beta framework to use this? :\

[Veedems Veteran]

so, you ported this to .Net 2.0 and now require us to use a Beta framework to use this? :\

585231876[/snapback]

The framework is stable as can be. I ported it over almost immediately after the released of 0.3 and it runs fine. The major problem with 1.1 framework was a horrible flickering bug in the text box region that could not be fixed. The 2.0 version corrects this bug and gives me a lot more room for expansion in the future.

[Elexir]

The framework is stable as can be. I ported it over almost immediately after the released of 0.3 and it runs fine. The major problem with 1.1 framework was a horrible flickering bug in the text box region that could not be fixed. The 2.0 version corrects this bug and gives me a lot more room for expansion in the future.

585231896[/snapback]

- Wasn't is so, like you need to declare kinda a buffer for it, so the flickering stops (richtextbox)

- The single instance thingy... I had code for it, if I'll find it, I'll post it. (It was 1 line of code, I remeber it was in the System.Diagnostics namespace.... anyway, lemme search.)

Nice Application :) (Y)