AngelsHolocaust
-
Content count
651 -
Joined
-
Last visited
Posts posted by AngelsHolocaust
-
-
Hi!
Cannot reproduce that.
Tried 2.31.1909 W32 with Win32 and Dos exe files.
Maybe you can give me a more detailed report?
Stefan / AH
-
Hi Dan,
I have quickly checked, and couldn't find a specific reason for this behaviour.
So, I have to put it on my long todo list. :)
All the best,
Stefan / AH
-
Hi everyone,
would anyone mind me stop calling NDN releases BETA?
I would upload each version as a full release (as I already do), just call it differently.
As I never upload new versions, which I consider unusable, the BETA version suffix
is really not needed. And in the running software you will never see the BETA string.
Any opinions appreciated!
All the best,
Stefan / AH
PS: This is my first try on a poll topic...
-
Hey Dan,
this was solved 2 days before: http://forums.muxe.com/index.php?showtopic=3202
:)
Strange, that this now suddenly appeared, as the problem in the fixed code
was there since quite some years.
In the above thread you can also download a fixed version, which outputs debugging
code on directory change. So this will not be usable for work but maybe you want to
test the bug fix.
Thank you,
Stefan / AH
-
Hi Dan.
As long as the first entry in the ini file
[Version]
IniVersion=20060926
remains unchanged, there have been no vital changes in the ini files.
Of course, some options were moved or removed, but I don't think it will affect your installation.
I always upgrade my installation at work and at home by simply copying over the old installation
and I keep *all* configuration files.
I only copy ndn.exe, english.*/russian.* and the subdirectories, the rest remains.
So, there should be no problems for you either.
Good luck :),
Stefan / AH
-
Hi!
THese are new history windows, like in several windos programs that open
histories on the fly while typing.
You can also turn these new histories off, but I tihnk it's quite useful.
1)
Drawing over inputlines in small windows is on my todo list.
(Not that easy to solve I fear)
There's a solution for you:
Hit the Ctrl or Alt button to close this enhanced history window.
2)
This should be fixed since v2.31.1909.
Please reply again if this is not the case.
All the best,
Stefan / AH
-
Hi Dan,
nice to see you back again.
Sorry, this is still not tackled.
But it's still 2008. ;)
All the best,
Stefan / AH
-
Hi Crimso!
You can turn that off in the menu
Options.File Manager.Setup.[ ] Don't quote LFN, clipboard.
Stefan / AH
-
Hi Crimso,
for every drive the current directory is stored in NDN.
It is an array from ['A'..'Z'].
The error was that drive characters were not upcased before
indexing into this array.
z is bad, Z is good.
Thank you for your help and bug report,
Stefan / AH
-
Hi again!
I think I have fixed the problem.
This is hopefully the last test version for you:
http://bnhof.de/~ho1459/temp/ndn_qd_dbg_4_w32.rar
Thank you,
Stefan / AH
-
Hi again!
Here's the next test version which again goes deeper into the code:
http://bnhof.de/~ho1459/temp/ndn_qd_dbg_3_w32.rar
Please upload the file again.
What OS do you use?
Thank you,
Stefan / AH
-
Hello Crimso,
it is very possible that I am not searching at the right place in the code.
But all I knew from you is that quickdirs behave differently than going into that directory
by "cd" or cursor keys and enter. So, I started searching in the quickdir code.
Let's check the command line handling:
http://bnhof.de/~ho1459/temp/ndn_qd_dbg_2_w32.rar
Please post the result again.
Thank you,
Stefan / AH
-
Hello.
Unfortunately, I could not see any error, so I extended the error output.
Please try this version and post the results again.
If there are too many files in the listing, please cut the list or upload the file somewhere.
http://bnhof.de/~ho1459/temp/ndn_qd_dbg_1_w32.rar
Thank you,
Stefan / AH
-
Hi again.
I have created a simple debugging version for you to test:
http://bnhof.de/~ho1459/temp/ndn_qd_dbg_0w32.rar
Do the following, after you installed it to a new directory (not over your original installation):
- add the network disk to your quick dirs
- goto the quick dir the same way as in the old version
- do you see the error again?
- send me the file C:\vp_debug_logfile.txt
Thanks for your help,
Stefan / AH
-
-
-
Hi Crimso.
This is really strange.
Of course I would like to have more information, but I don't know what to ask for. :)
The best thing of course would be if you could find the reason why NDN behaves like that.
Is "z:\distr\gransmeta\liveupdate" the bad directory?
And it only happens if you change the directory by quickdirs?
Can you recreate this error?
If yes, I could try to make a debug version which would save information
on what is wrong when accessing this directory.
Stefan / AH
-
Hi Crimso and again sorry for the late reply.
I am quite busy at the moment. :)
I have saved the image and the link to this thread.
I cannot work on this at the moment but I have added this to the todo list.
Yes, it is me.
I have taken over the work from Necromancer 5 years ago.
Thank you for your support and comments,
Stefan / AH
-
Hey,
nice to hear from you.
And thank you for the comments.
All the best,
Stefan / AH
-
Hello Crimso,
sorry for the late reply.
The problem with these symbols (characters > 127) is that every language can redefine them.
For example, I created a new XLT file for this release to be able to display the german windows
codepage correctly:
õä÷ö³ü▀ß─ÄÍÖ▄Ü
(Umlauts and ß)
I suspect the current implemented WIN codepage to be specifically for russian users,
or am I wrong? We should probably try to get a default WIN charset from the
operating system in the country setup.
The WIN codepage is fixed and built into NDN.
As long as I don't get the default table from the OS this problem remains for any user,
using a different codepage than russian.
Your only choice right now is to create your own .xlt file.
What country codepage are you using?
MAybe this is a bug in the russian implementation of the current WIN codepage.
Stefan / AH
-
Hi everyone!
Just in time before october. Enjoy!
─════┤ v2.31.1909 DPMI32/WINDOWS/LINUX 27.09.08 ├═══════════════════════════─ [-] commented an unecessary instruction from system.ChkResult() [V] {C} [+] added a 'doc\readme.1st' file with basic information [*] added ctNoChange|ctCapitalizeFirstWord to stringsx.tCaseType and stringsx.FormatStrCase() [+] added mathx.divmod32() REGULAR EXPRESSIONS/PCRE [*] added new PCRE v7.7 {C} -> added PCRE version output if NDN is not started quietly to main.TellOS() -> added new PCRE77.LIB, sent updated files to PCRE Philip Hazel (PH) -> added PCRE.TXT to the DOC\ subdirectory and updated the PCRE online help -> added new options to the resources/help and Options.Configuration.Miscellaneous Setups.Regular Expressions -> D32: PE2LE requires the lib to be compiled with the -B (ASM compile) switch because of the unsupported _TEXT segment in the resulting NDN.EXE [-] Replace: $' inserted one character too much [N] -> removed a bad "length+1" from pcregexp.TpcRegExp.GetPostSubStr() [-] Replace: $` didn't add the first character [N] -> removed a bad "length-1" from and changed a pchar offset from 1 to 0 in pcregexp.TpcRegExp.GetPreSubStr() [+] Support for more RegEx replace options/operations -> modified pcregexp.TpcRegExp.GetReplStr() -> now handles: n = [0-9] name = named subpattern * [\$][&`'+_] * [\$]n, \[UuLlFfIiTt](n| [{<'] n+ ['>}] ), [\$] [{<] n+ [>}], \gn+, \g [{<'] n+ [}>'], \k [{<'] n+ ['>}], (?P=n) * [\$] [{<] name [>}], \'name', \g [{<'] name [}>'], \k [{<'] name ['>}], \[UuLlFfIiTt] [{<'] name ['>}], (?P=name) -> modified pcregexp.TpcRegExp.MatchSub() to handle relative backrefs -n VIRTUAL FILE SYSTEMS (VFS) [-] FTP: restoring to source dir didn't work with "C:/dir/" paths [A] -> corrected the path extraction in vfs_ftp.ParseFTPURL() -> changed directory appending in vfs_ftp.ftp_StoreFile() [-] NETW: Kyrillic names are correctly displayed [A] {G} -> added keymap.(Ansi_Ascii|Ascii_Ansi)() usage to network.(GetResources|AddNetworkDrive)() CALCULATOR [-] fixed "101o OR 1"/FLOOR bug [C] {C} -> modified calc.DoEval() "or" operation [*] decimal and thousand separators weren't taken from country info [DNOC] -> moved the dialog data connection from calc.ConvertValueToString() to calc.ConvertDialogData() -> calc.ConvertValueToString() is now used in calc.TIndicator.Draw() -> modified calc.GetValue() so that calc.GetValue().Get(Hex|Bin|Oct)() now use calc.GetValue().GetValueBase(), as the code was identical except for the base for the data conversion -> added conversion options to commands: co(Dec|Hex|Bin|Oct|Exp|Sys) -> added calc.ConvertSeparators() [-] character values didn't work with characters used in operations (+-*) [A] -> modified calc.DoEval() to preconvert these values in first run -> removed calc.GetValue().GetCh() TURBOVISION: VIEWS/DIALOGS/MENUS/OBJECTS/MESSAGES [+] window explode unit by Candyman {C} -> added vexplode to the source tree, with little modifications for NDN -> added new configuration combobox "Win Explode" to Options.Configuration.Interface (eg. ndn.dnr) -> added WindowExplodeDelay to startup.InterfaceData, which will be handled in dnini.Proceed() -> added views.gfExplode, modified views.TView.Hide(), TGroup.InsertBefore(), TWindow.Init(), dialogs.TDialog.Init(), menus.TMenuView.Init() EDITOR/VIEWER/DBVIEWER/WKZVIEWER(Spreadsheet) [-] "Goto file" by clicking right on the title frame didn't work anymore [A] -> dnapp.GlobalEvent() didn't fill in Event.Command [+] added new filter for windows to german translation: WIN2GER.XLT FILE PANEL [-] crash on RMB press on border "═" on the current directory line [A] (nal49@mail.ru) -> flpanelx.TFilePanelRoot.CommandHandle().cmFindGotoFile didn't check for empty strings HISTORIES [-] Smart histories: draw cursor on current position when openened [A] -> added dialogs.TInputLine.History, removed dialogs.THistory.InitNewHistory(), added dialogs.THistory.Awaken() and modified dialogs.TInputLine.SetState() DBF VIEWER [-] crash when loading files created by "Visual FoxPro" [A] {G} -> default variables were not initialized in dbfview.TDBFile.Init()
Download: http://ndn.muxe.com/download/
All the best,
Stefan / AH
-
Hi!
Unfortunately I cannot see your screenshot (cannot access your forum without registering).
But I think that you see a lot of "?" on screen?
NDN doesn't support UTF-8 encoding yet, so you cannot see most characters > 128 correctly.
But it's on the todo list.
Stefan / AH
-
Hi asz!
It took me a while to find time to answer your post...
I agree on all your arguments except for the last 5.
Why is contribution to non open source projects (NOSP) (mostly) wasted (time?) ?
Is a bug report for an OSP better than for a NOSP?
I like the "idea" behind OS. More on this point in the last argument...
NDNs licence allows binary redistribution on free media.
Only on media to be sold I want to be asked at least.
The source code itself is a total different issue.
But, the source code goes to everyone who asks for it, after telling me his interests and goals.
--------
Last argument, and most important: disadvantages
First of all, my views on OS are not as strict anymore, I discussed this with
Necromancer quite some time ago and he would provide me with a CVS/SVN server.
But I do have some concerns (disadvantages) that I want to express here:
- time to set up the whole OS project
My time is quite limited. I rather spend it all on NDN itself.
I don't know how long it will take me to complete an OS-NDN setup.
- time to maintain incoming contributions
Again, time! Right now I get source code by a very few people, which I test and verify before
it is actually included into the source code.
I fear that I will get a lot of patches (probably directly patched on the server)
and that I have to maintain the patches over the server, with a lot more overhead
that I do right now. Maybe I will get more patches, maybe a lot of "waste".
My own time to work on NDN will decrease...
- NDN branches
How can I keep people back from creating loads of new branches of NDN instead of
contributing to the main branch?
And again, adding more and more patches, with testing and so on.
- NDN stability
NDN is quite stable by now.
My biggest concern is losing the overview and ruining my past years of work.
Probably I am a bit overconcerned.
I am not saying NDN will never go OS anymore.
But at the moment, at least I, cannot put any effort into this.
Stefan / AH
-
Hi!
I just have released a new NDN: http://forums.muxe.com/index.php?showtopic=3197.
Konsole (and many others) has one problem: moving the mouse into the konsole window stops the
keypress/release events... But, when moving it out everything works fine.
I will work on this, grabbing the complete keyboard f.ex. helps. :)
The ? on screen are probably due to the fact that NDN doesn't support UTF-8 yet.
If you hit CTRL-B, you should see all the characters used by NDN. You should also
see a lot of ? there.
As for the keyboard layout, I am not sure if this is a NDN issue. Maybe you can offer me
a test scenario for this? Switching between us and german layouts does work correctly in
NDN.
Hopefully you can use NDN now,
Stefan / AH
New Release: 2.31.2305
in Development
Posted · Report reply
Hi!
Not much to say, except that I am late again. :)
Whatsnew:
Download: http://ndn.muxe.com/download/
All the best,
Stefan / AH