Jump to content
Muxe Inc Forums

dandv

Members
  • Content count

    368
  • Joined

  • Last visited

Posts posted by dandv


  1. Looks like I have a special ability to find bugs in NDN.

    Fortunately, AngelHolocaust has an even higher ability to fix them! :-)

     

    Doesn't this seem strange to you?

     

    I mean, how many bugs can a person find? Eventually, those bugs get fixed, the software gets better and better, so there should be fewer bugs to be found. But I still find bugs in every new beta.

     

    I was about to mention an analogy with gold miners: maybe you are lucky and find gold somewhere, and find some gold nearby, but how much gold can you find? And there are other gold diggers, too.

     

    I think the difference is in how finite "gold" and software are, more than in the rate of exhaustion. That means, you can be a good gold digger, but eventually there will be no gold to dig. While for software, if you are a good bug finder, will you be able to find bugs forever?

     

    What do you think?


  2. hi!

     

    there were quite some problems with executing, which i all fixed

    ("note pad.exe" "a gb c.txt" or LFN in external view/edit in 7104!)

     

    Right, I understand now.

     

    the archiver gui check is a side effect

     

    i will disable this effect for archivers

     

    Does that mean that an archiver called "C:\Program Files\arch.exe" won't work?


  3. hi!

     

    this is no bug, in fact, NDN behaves exactly as it should

     

    you are calling a GUI program to handle the archives, NDN detects that and returns to

    the commandline after executing, deleting the files it created.

     

    Then why does NDN beta 7104 work flawlessly, with the same GUI program?

     

    this works better than ever with the new version (obviously)

     

    I had no problems with the old version. What was wrong with the old calling model?

     

    the only solution would be not to delete the files at all or to delete them before executing new programs

    although, it's not nice

     

    How about NDN leaves xxndnxx.lst alone, until the next archiver operation, and rewrite it then? This would save a "delete" call each time. And when NDN exits, it could delete xxndnxx.lst

     

    Is it "nice" to leave a file in the %TEMP% folder? Maybe not, but for example in Windows 2000, my TEMP folder always gets filled with all sorts of crap: every time you run MSWord 2003, it creates folders like msohtml or msohtml1, something else creates hsperfdata_Administrator, Acrobat updates create an Adobe folder, VMWare keeps some TMP and LOG files that you can't even delete, and so on. So NDN keeping one file while it's running is a minimal problem. The file could even be kept in the NDN folder.

     

    I think this would be more convenient for new NDN users than having them fail to use GUI archivers. How many will check the forums for the alternative solution (hack) that GFault provided?


  4. When archiving several files, NDN creates a list of the files to be archived, then calls th archiver.

    In beta 7555, NDN deletes the list file before the archiver gets a chance to read it. This way, WinRAR complains that is could not find %TEMP%\xxndnxx.lst .

    In beta 7104, NDN behaved correctly, with the very same archiver definition, listed below.

    [ZIP]
    UseLFN=1
    ListChar=@
    BestCompression=-m5
    GoodCompression=-m4
    NormalCompression=-m3
    FastCompression=-m2
    FastestCompression=-m1
    StoreCompression=-m0
    Solid=-s
    RecoveryRecord=-rr
    SFX=-sfx
    ForceMode=
    ExcludePaths=-ep
    IncludePaths=
    Test=t
    Delete=d
    Garble=-p
    Move=m -afzip
    Add=a -afzip
    ExtractWithPathnames=-ext -directories
    Extract=-ext
    Unpacker=pkzipc.exe
    Packer=winrar.EXE

     

    I used Sysinternal's Filemon to monitor NDN's file accesses and it confirmed my assumption. Please find attached the logs. To open them, download Filemon 7.02 and click File, Open.

     

    Until this issue is fixed, I cannot use NDN to archive files, so I have to revert to beta 7104.

    xxndnxx.lst_deleted_too_son.zip


  5. In Windows, you cannot create a filename with spaces at the end.

     

    1. In NDN, move some file to a non-existent folder "a \" (notice the space at the end of the folder name).

    2. NDN will offer to create the directory, but the directory that gets created will not have the trailing space.

    3. Then, NDN will attempt to move the file to "a \", which doesn't exist.


  6. Transfer a large file via FTP.

    1. Press ESC. After a (short) while, the transfer will stop.

    2. Press Enter. After a (short) while, the transfer will stop.

    3. Click the button using the mouse. The transfer will not stop, although you can see the button being depressed.

    4. Press Space, the TVision shortcut for pressing the active button. The transfer will not stop.

    5. Press 'S', the button's shortcut. The transfer will not stop.

     

    My guess is AH has implemented custom handlers for 'Enter' and 'ESC' in order to 'multithread' the transfer... ?


  7. Congratulations for beta 7104!

     

    Looks like the 'cursor placement on new dir' and 'file edit history color' bugs are still there. I played with creating directories again and here's what I found:

     

    In an empty directory, create these directories, in this order:

    1. 1 - NDN places the cursor on the new directory
    2. 1' - cursor stays on '1'
    3. 99 - cursor stays on '1'
    4. abc - cursor stays on '1'
    5. z - cursor moves to 'z'
    6. dandv - cursor stays on 'z'
    I guess I could try some more names and infer the logic behind this, but probably it's a tiny bug that AH will be able to fix ASAP.

  8. In NDN.EXT I have:

    pdf {"C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe" "!:!\!.!"}

    In NDN.VWR I have:

    pdf: "C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe" "!:!\!.!"

    In NDN.EDT I have:

    pdf: "C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe" "!:!\!.!"

     

    When I press Enter of a PDF, NDN correctly launched Adobe Reader.

    When I press F3 or F4 on the same PDF, cmd.exe returns the following error:

    'C:\Program' is not recognized as an internal or external command, operable program or batch file.


  9. On a related note, even if NDN wraps at spaces only, I think Ctrl+Shift+Left/Right should stop at any punctuation. Consider the example below (the underscore represents the cursor):

    sub _my_subroutine_with_arguments($) {
        ...
        return;
    }

     

    If I press Ctrl+Shift+Right_Arrow, I expect only the word "my_subroutine_with_arguments" to be selected, but NDN will select until "return".

     

    What do others think?


  10. OK, I work in software localization and we also do a lot of DTP.

     

    As a general rule, punctuation is always stuck to the word before it and you only wrap on spaces, except on words longer than the line length, which are nor broken.

     

    As a more official opinion, I would recommend that NDN conforms to the wrapping standards of today. One very good standard is the W3C HTML 4.0 specification, which states:

     

    "In Western scripts, for example, text should only be wrapped at white space."

    http://www.w3.org/TR/html4/struct/text.html#h-9.3.5

     

    I have also attached a sample HTML (home.arcor.de/dandv/wrap.html) that lets you test wrapping.

    Opera 8.51: wraps according to the HTML 4.0 specification

    IE6.0: can wrap before the following characters: ( [ { -

    Firefox 1.5.0.1: no wrapping (!??)

     

    Finally, I would like NDN to "virtually wrap", that is, not insert actual CR/LFs when wrapping. It should only display the text as wrapped, and keep the CR/LFs that it found in the file.

    wrap.html


  11. #4

    press shift-tab in any dalog - dialog disappears (visualy)

     

    I pressed Shift+Tab in Calculator (Ctrl+F6) (which isn't exactly a dialog) and in "System Setup". None disappeared. NDN 2.15.5814.

     

    #2

     

    Options -> File Manager -> New Manager defaults... -> Sort by...

    Do not work (always sort by name in new manager)

     

    Confirmed!

×