John Labenski <jlaben...@gmail.com> wrote: (06/03/2009 03:13) >On Wed, Mar 4, 2009 at 3:15 AM, lostgallifreyan ><lostgallifre...@gmail.com> wrote: >> >> No strangely large values for the drop position? I often see them, with >> large file counts. 10137 seems to be constant for X when it happens, the Y >> value is variable but is huge, 13nnnnnn, with first n usually 6, sometimes >> 7. No idea what it means though. I managed to crash it with several thousand >> files, this time with User.exe. >> > >It might be because you're using Win98. wxWidgets 2.8 is really geared >towards Win XP which is already about seven years old. I would suggest >moving to Win 2000, if possible, since my experience is that it runs >at least as fast as Win98 and doesn't crash. Just a suggestion...
Not moving. But your suggestion of W2K is a good one. :) I liked that OS better than WXP, the few times I tried it, and I'll look at it again. But I depend on W98 for hardware and some software, and the raw DOS underpinning too. Too many reasons to stay. But those are MY reasons, so here is a reason that might be far more useful to you and others: http://www.msfn.org/board/index.php?showtopic=128308 Several posts there say something I've long been aware of, but far better than I usually say it, and some of them are serious coders whose views carry some weight, (especially Rudolph Loew who has posted elsewhere on that forum, who is firmly staying with W98 and who sells patches for various aspects of it, one of which I use to get 48 bit LBA addressing for large hard disks). The problem is not so much the OS, but the program, and that later OS's allow lazier coding because they hide flaws better. While I learn wxLua, I think it gives me yet another excellent reason to stay with W98. If my code works on on this, the chances are that it will work right elsewhere, leaving only specific details of other OS's to attend to as noted in the docs I've seen. That wxLua and wxWidgets persist in supporting W9X is a Good Thing. I'm very pleased about that. The drag-drop problem might easily be fixed by limiting dropped files to 10 or 50, and where precise location on a GUI is important, I guess it makes sense to enable dropping on a single widget rather than the whole frame and getting co-ordinates. There can be several ways to work round this. Getting mouse position onLeftUp, for example.. PS. I'll be getting 1 GB of RAM to use instead of 512 MB. Amongst changes needed to make that work well, I've read that the [vcache] settings in System.ini include namecache and directorycache values. That first one might directly help the drop-files problem, if it does I'll post again. I won't know for a while because testing vcache settings isn't a thing that can be evaluated fast. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
