But if it's not opened then it will ?
I have to test later when i get home...
On Tue, Aug 25, 2009 at 9:22 AM, Andreas Krinke wrote:
> Daniel Aquino wrote:
>> hm yea ok i guess that is fine...
>>
>> i was setting verbose true and then not opening the window which
>> caused a pop up...
>>
>> i gu
Daniel Aquino wrote:
> hm yea ok i guess that is fine...
>
> i was setting verbose true and then not opening the window which
> caused a pop up...
>
> i guess if i close the window then it should be set back to false...
No, that's not nescessary. Once a log window was created with the last
argum
hm yea ok i guess that is fine...
i was setting verbose true and then not opening the window which
caused a pop up...
i guess if i close the window then it should be set back to false...
thanks...
On Tue, Aug 25, 2009 at 8:57 AM, Andreas Krinke wrote:
> Daniel Aquino wrote:
>> yea but that mean
Daniel Aquino wrote:
> yea but that means you have to create the window.
>
> I guess at that point you could write a small wrapper function that
> would only call wxLogVerbose if the window has been opened...
>
> But I was going for the simple approach of having wxLogVerbose lines
> in my app whi
yea but that means you have to create the window.
I guess at that point you could write a small wrapper function that
would only call wxLogVerbose if the window has been opened...
But I was going for the simple approach of having wxLogVerbose lines
in my app which only took affect if the window w
Daniel Aquino wrote:
> but I was referring to , "web browser alert style boxes" vs "a log
> window". If the log window is closed it should not produce, "web
> browser alert style boxes"
Setting the last parameter of wx.wxLogWindow() to false seems to solve
the problem:
local log = wx.wxLogWindow
Well the thing is if the wxLogWindow is closed then the default
behavior will produce those alert dialogs...
I really don't want that...
I have a small function which I use for that purpose.
On Mon, Aug 24, 2009 at 11:26 AM, John Labenski wrote:
> On Mon, Aug 24, 2009 at 11:12 AM, Daniel
> Aquin
On Mon, Aug 24, 2009 at 11:26 AM, John Labenski wrote:
> On Mon, Aug 24, 2009 at 11:12 AM, Daniel
> Aquino wrote:
>> hm ok I'll look into that...
>>
>> but I was referring to , "web browser alert style boxes" vs "a log
>> window". If the log window is closed it should not produce, "web
>> browser
On Mon, Aug 24, 2009 at 11:12 AM, Daniel
Aquino wrote:
> hm ok I'll look into that...
>
> but I was referring to , "web browser alert style boxes" vs "a log
> window". If the log window is closed it should not produce, "web
> browser alert style boxes"
>
You mean a wxMessageDialog? A dialog with
hm ok I'll look into that...
but I was referring to , "web browser alert style boxes" vs "a log
window". If the log window is closed it should not produce, "web
browser alert style boxes"
On Mon, Aug 24, 2009 at 11:01 AM, John Labenski wrote:
> On Sun, Aug 23, 2009 at 9:57 PM, Daniel Aquino
> w
On Sun, Aug 23, 2009 at 9:57 PM, Daniel Aquino wrote:
> If I do:
>
> wx.wxLog.SetVerbose(true)
> wx.wxLogVerbose("blah")
>
> I still get a pop up window :[
>
> I only want the log window to be for informational purposes...
I thought you wanted a popup window for your messages? I never look at
the
If I do:
wx.wxLog.SetVerbose(true)
wx.wxLogVerbose("blah")
I still get a pop up window :[
I only want the log window to be for informational purposes...
When it's closed or never created then it should never show pop up messages...
Is this possible?
Also when I create a wxLogWindow and then c
Daniel Aquino wrote:
> But nothing shows up in the log window and i don't know how to enable
> verbose logging.
Try this:
wx.wxLog.SetVerbose(true)
-- Andreas
--
Let Crystal Reports handle the reporting - Free Crystal R
local log = wx.wxLogWindow( frame, "Log", true, true )
wx.wxLogError("testing...")
--wx.wxLogWarning("")
--wx.wxLogMessage("")
--wx.wxLogStatus("")
--wx.wxLogDebug("")
--wx.wxLogVerbose("blah")
That's basically all I have right now.
If you d
Well I really just want a log window that only shows messages if it's open.
I do not want the messages to show up as alert boxes when the log
window is closed.
I believe I need to enable verbose logging but can't seem to figure out how.
I don't have access to my code right now, when I do I will
On Fri, Aug 14, 2009 at 9:29 PM, Daniel Aquino wrote:
> wxLogMessage appears to not send an alert window when the log window
> is open but it does when it's closed...
>
> Really I'm just looking for a debug method to send to the log window
> and not interfere with the other log messages..
>
> log =
wxLogMessage appears to not send an alert window when the log window
is open but it does when it's closed...
Really I'm just looking for a debug method to send to the log window
and not interfere with the other log messages..
log = log window
log:SetVerbose(true) seems to crash
I tried log:SetLo
I seem to see messages when I do LogError but not LogVerbose
On Fri, Aug 14, 2009 at 9:12 PM, Daniel Aquino wrote:
> The application also appears to crash which must mean I need to clean
> up the log window some how on close...
>
> On Fri, Aug 14, 2009 at 9:09 PM, Daniel Aquino
> wrote:
>> I crea
The application also appears to crash which must mean I need to clean
up the log window some how on close...
On Fri, Aug 14, 2009 at 9:09 PM, Daniel Aquino wrote:
> I created a wxLogWindow successfully and attached it to my current window.
>
> I called wxLogVerbose but don't seem to see any output
I created a wxLogWindow successfully and attached it to my current window.
I called wxLogVerbose but don't seem to see any output.
The error functions work fine (showing a pop up window).
I noticed I had to bind wxLogWindow to a particular frame but then
when I call the log functions I doesn't n
20 matches
Mail list logo
