John Labenski <jlaben...@gmail.com> wrote: (29/05/2009 20:02) >Please turn on your line wrap. >
Can't.. nPOP (mail client I use) only does that for viewing, which I thought was kind of the point, a sending client can't know what size remote viewers will use, unless they're all the same. Actually, the Usenet client Xnews does set wrap on sent text, as do some others, and by the time a few posts get repeat quoted the result is scrambled to near illegibility, it's a terrible idea. :) >> >> The new error reporting method doesn't work well. While I know someone asked >> for >> it to print messages to the console, that's broken more than it fixed. Now, >> if there's an >> error, the program exits, reporting nothing. (I launch scripts by using >> WIndows to >> associate them with wxLua.exe. If I try launching them from a commandline, >> nothing >> is reported there either, so I try launching them from wxLua.exe directly. > >This is unfortunate. I use Cygwin as my console in MSW and it does >provide stdout. GUI programs in MSW merely throw out anything written >to stdout. There is nothing that we can do about that besides allocate >our own DOS console, but this new console can only exist while the >parent program is running. I think the best solution is to make using >our own console standard in MSW since it will stay open until you >close it. i.e. make "$wxlua.exe -c" the normal mode of operation in >MSW, but only show the console when something is printed. > stdout might have worked ok but I think wxLua not actually being a consol app just got launced by the console then ran as it normally would. Ideally I think the answer is to have an INI file attached to wxLua and let us choose which method we want from each of those that have worked well. >>This is clumsy, drag/drop won't work as it does if I launch by dragging to >>the file's icon >> in a directory (but that doesn't report errors now). Dragging onto the >> pre-opened >> wxLua fails because it's not enabled for drag/drop, so I must browse >> manually to the file. > >Fixes or additions to editor.wx.lua are welcome. > I thought wxLua was a C-coded binary. But I did notice that the Lua script produced what appeared to be the same thing. I think you mentioned this a month or so back, but I still manage to get confused by this. How much of the wxLua editor is actually Lua? I wasn't sure it was within my reach to examine and fix internals of that one.. My guess is the script access core stuff in the binary, but it won't be the work of five minutes to figure out how much control we get from the script... I noticed same behaviour regarding space chars in either form, and putting the script out of reach of the binary implies that the common code handling that is in the binary anyway, so I have no fast way to figure out what I can control, and good reason to ask if I even can.. >>That fails too because it doesn't recognise spaces in file names! This is >>definitely not >> an improvement. While the script does open in wxLua, it won't run because >> even though >> it has it opened, it can't actually FIND it by file name to run it. > >Really? I have no problems opening files with spaces in its name. >Please give more details. > Not much I can add, but there is some... I open the file "GPS Chart/lua" by manually browsing from the v2.10 wxLua, then try to run it from the Debug menu. A "wxLua Console" window pops up saying: Lua: Error occurred while opening file cannot open C:\WINDOWS\Desktop\GPS: No such file or directory Lua: Error occurred while opening file As you can see, it appears to have balked at the space. I double-checked that it IS a space. :) (Seriously, I was using a PPC for a while and beat just suck a problem as this by using char 160 to dupe that system into reading the whole name. Same trick fails in this case though, and actually causes the initial file load to fail also. Note: System is W98 SE. Probably not significant though. >> (How about an option to send error reports to a file? That way I can see >> them as before, >> in a message box, but also have a written copy if I need one). > >$wxlua.exe myprogram.lua > outfile.txt > That's cool. Works too, wasn't expecting that as I thought it was purely a GUI program even if launched from a console. Might be nicer if we could choose such an option and leave it set in INI file though, as otherwise invoking this behaviour automatically demands some fancy footwork with the registry in Windows and might even conflict with command structures like those I use to associate data files with a script that is in turn associated with wxLua. Command lines can only do so much at one go.. > >> Another thing I have found is a failure in EVT_ERASE_BACKGROUND blocking. >> I'm getting >> flicker in something that didn't flicker in the previous release of wxLua. >> Note the two commented lines... > >Please try to provide a minimal runnable sample. I see that you are >still using the wxStaticBitmap, I assume the flicker you see is from >that control? > I reduced as much as possible, I think. Context can only be stripped down to a limited extent. You need the code that moves the image, and which sets up the layer that takes input control, and that OnSize function is vital, it prevents the image from drawing all over the frame borders, by constraining it to draw on panels correctly sized. Changing any of that would mean writing an irrelevant sample. Yes, it is that wxStaticBitmap, but it worked before, should work now. As far as I can tell, it looks like the error is in wxWidgets itself most likely, someone must have decided that it ought to allow background erasing, and enabled it but where last time it could not be enabled, this time it cannot be DISabled. >:) Eventually someone might notice. I might tell them, not sure if they'll listen to me though. Someone 'fixed' the spincontrol events a while back and actually broke what was more useful bahaviour before the fix! I spoke to Kevin Hook about it, and he said he's not involved now. Ò^O, I figured that if HE wasn't involved, I was about as close as the orbit of Jupiter. My earlier sample is ready to run, just needs an edit to point to a big bitmap. (I didn't think people would take kindly to me attaching big bitmaps here. :) ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
