On Thu, May 28, 2009 at 8:05 AM, lostgallifreyan
<lostgallifre...@gmail.com> wrote:
>
Please turn on your line wrap.
>
> 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.
>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.
>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.
> (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
> 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?
Regards,
John
------------------------------------------------------------------------------
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
