Recommended Posts

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?

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.

  • 3 weeks later...
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.

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

  • 2 weeks later...

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.

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.

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:

post-1798-1104877145.jpg

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.

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)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Google are hyprocrites for signing this. They have been pulling the same dirty tactics as Microsoft, only they do it on Android and ChromeOS.
    • In some countries the law has forced Microsoft to display a menu on a fresh install of Windows which asks which web browser you want and it will install that browser. This doesn't add any bloat to Windows. It simply an additional step when setting up a new PC.
    • Chrome is also a first party browser on Android and ChromeOS. And on those systems, Google is pulling the same dirty tactics as Microsoft does on Windows.
    • Unofficial script lets you install unreleased Windows 11 features without Microsoft Account by Sayan Sen Microsoft has been steadily evolving the Windows Insider Program over the years, introducing new channels and testing paths that allow enthusiasts to experience upcoming and yet-to-be-released Windows features (some interesting hidden ones too) before they reach the public. However, one long-standing requirement has remained largely unchanged as users are generally expected to enroll in the Program and with a Microsoft account. That's where a third-party tool called "OfflineInsiderEnroll" can help. OfflineInsiderEnroll is said to be a lightweight script that enables access to Windows Insider Program builds on systems that are not signed in with a Microsoft account. Essentially the tool configures the necessary Insider settings locally and hence allows users to select and switch between available preview channels while continuing to receive builds through the normal Windows Update channel. If you are wondering how it manages to do so, it is made possible by a Registry value known as TestFlags. When configured to"0x20", Windows stops communicating with Microsoft's online Insider enrollment services thus preventing locally configured Insider settings from being overwritten. This allows the script to apply its own channel configuration directly through the Registry as Windows Update does not verify whether a device has been officially enrolled in the Insider Program or not. Previously the utility has had already supported the traditional Insider branches including Dev, Beta, and Release Preview. However following Microsoft’s recent restructuring of its preview channels, the script has now been updated. The latest OfflineInsiderEnroll version, 2.6.6, adds support for the newly introduced Insider channel lineup. As such, users can now choose from several Experimental channels in addition to Beta and Release Preview options. The update also retains tools for refreshing the Insider cache, resetting Insider settings, and completely stopping Insider enrollment when needed. Keep in mind though that will need elevated privileges when running the script (run as Admin). You can get the latest version of OfflineInsiderEnroll from this page on its official GitHub repo.
    • The "Classic" Outlook has done that for a few years as well. The option to even change that is really hidden away too... It really shouldn't be hard to respect user defaults. Sadly we are the product now, not Outlook. To change in the Classic Outlook: File > Options > Advanced > change "Open hyperlinks from Outlook in"
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!