I cannot redirect log messages when building GUI applications in wxWidgets. I've tried the following snippet
delete wxLog::SetActiveTarget(new wxLogStderr()) ;
so that every call to wxLogXXX would cause a message to be print in the standard error output, not as a message dialog presented to the user. However, it had no effect, and logs continue to be present as dialog messages.
Am I missing something?
Regards.
Try removing the delete. Simply call SetActiveTarget
wxLog::SetActiveTarget(new wxLogStderr()) ;
Here's what it looks like in my IDE ( VS2008 )
Related
I'm trying to remove the Routing App Coverage .geojson file. Every-time I try to remove this and save changes, I get this error:
We’re temporarily unable to save your changes. Please try again
later.
It's been 2 days now. I still can't remove it. If I try to change any other field in the app submission form, it works. Just not the Routing file.
Here is what happened that led to this point:
I tried to submit an app with a valid .geojson file
I got an Invalid Binary error and the app was not submitted. This is because my app does not support routing.
I try to remove the Routing .geojson file from my submission form.
It doesn't work. I keep getting the error " We’re temporarily unable to save your changes. Please try again later. "
Error keeps occurring after 2 days.
I have no idea what is wrong. Please help. Thanks
I do not know if you have solved this, but I had the same problem. Just inspect the element (that pop-up that appears on top of the Routing App coverage), delete the element from browser's tree and press the delete button.
I'm loving IntelliJ because I also work with MySQL and the integration into one UI is great. Seems that IntelliJ works nicely with ColdFusion as well. I'm just hoping to successfully use MXUnit, but I seem to be getting an error upon testing. My main goal is just being able to display the output directly in IntelliJ instead of outputting in a browser.
My test site path: /Applications/ColdFusion11/cfusion/wwwroot/Test/test.cfc
Error http://localhost/mxunit-launcher.cfc?method=executeTestCase&componentName=test
Seems like I have to add in a mapping, maybe in CF Admin, because the path and web path don't match but I haven't done that before if that's the case. Here's a screenshot of input in IntelliJ, and the output at the bottom of the screenshot when running the debugger:
Thanks for any feedback on what I might be missing.
I have installed Hue-2.5.0 in pseudo mode and also i am able to view the UI.
Beeswax(hive UI), sqoop, oozie editor everything are working efficiently but i dont know why my pig scripts are not working, UI is non resrponsiv & it is not showing any errors or exceptions.
i have checked logs also and found no issue
what could be the issue???
thanks in advance.
You should look at http://hue_host:8888/logs, or right click and 'inspect element' and look for error in the Chrome console. You can also share a screenshot of what happens when you clicked 'submit. Feel free to comment on the hue-user list too.
I have console applicaiotn that currently uses CAsyncSocket.
I need to implement SSL so after some searching I found this project: http://www.codeproject.com/Articles/3915/CAsyncSslSocketLayer-SSL-layer-class-for-CAsyncSoc
For some reason same simple code that works fine on GUI code does not work in console app.
Has anyone exp. with CAsyncSslSocketLayer ?
Thanks.
CAsyncSocketEx uses a window as a sort of cheap thread to handle the event notifications that come from select(). Unfortunately, if you don't have a message loop, then the window which it creates will not receive these events.
http://support.microsoft.com/kb/90975
This article explains that a call to CreateWindow() needs to be called from a thread which has a message loop. And if you don't, then anything sent via PostMessage() won't get there.
I've recently started to tinker with this -- I want to remove the annoying hidden window and replace it with a normal thread. Their code relies on WSAAsyncSelect() in order to receive socket events... to a window. Yuk!
It's been a while since I had the same problem, but if I remember correctly, to use CAsyncSocket in a console app you need to add something like DECLARE_CONSOLEAPP (first two links shown below) to your console app. This should give your console a message pump to generate the socket notifications (OnReceive, etc.) GUI apps have these pumps but console apps don't, generally. The third (msdn) link below might also apply, it has more info and a different way.
If these still don't work, you should put breakpoints in your socket code and make sure your socket isn't instantiated in a thread or callback other than the main console app (the one that now has the message pump).
I think googling around for 'CAsyncSocket WinApp' or 'CAsyncSocket console app' would show more.
http://www.codeguru.com/cpp/misc/misc/consoleapps/article.php/c243/Console-app-using-MFC.htm
http://troels.knakkergaard.dk/code.htm
http://social.msdn.microsoft.com/forums/en-US/vcgeneral/thread/a6f1b72a-21d8-4046-a3dc-d7d29ece2ef6
I've just started with orbeon and xforms for some project.
I have Orbeon succesfuly integrated with my test application as xforms engine (separate deployment with crosscontext).
Now, xforms basics are behind me and I needed to implement some kind of error checking after submit. So I'm trying to handle xforms-submit-error for example like this (this is modified example from w3.org):
<xf:submission action="/processor500" method="post" id="submission1" replace="none">
<xf:message ev:event="xforms-submit-error" level="modal">submission1 error (<output value="event('response-status-code')"/>)</xf:message>
</xf:submission>
/process500 is empty servlet, which just raise RuntimeException so it is returning 500 response code.
But response-status-code in event is allways empty. Any of event properties are allways empty and i just can't figure it why (google didn't help this time).
Any suggestions?
Thanks.
event('response-status-code') on xforms-submit-error is supported, and your example doesn't work most likely because you're missing a prefix on the <output> (it should be <xf:output>). Also see this XForms test case showing the event('response-status-code') in action.