OK, that was an easy fix. That app was having problems parsing the
command line args.
Patrick Hartling wrote:
> Todd J. Furlong wrote:
>> A quick follow-up to my previous email. My devices fail to initialize,
>> too, so it's not just the display. I've attached the full Juggler debug
>> output this time.
>> Todd J. Furlong wrote:
>>> I'm porting a number of applications to Juggler 2.2, and I've hit an
>>> odd snag with one of them. Using the standalone.jconf configuration
>>> file (and other simulator-only configurations), the application does
>>> not open a window.
>>> If I print out debug info, this is the last I hear from the draw manager:
>>> [0016761/000] vrjDRAW:vrj::GlDrawManager started (thread: 0016761/001)
>>> The application stays alive (processor usage is high and preFrame is
>>> getting called), so it looks like some part of the window
>>> initialization is hanging.
>>> I will start digging into the source code to see why this might
>>> happen, but I thought I'd throw it to the list as well.
> According to the output that you posted, you are not loading a configuration
> file. The output does not reference any input devices or display windows,
> nor does it display any .jconf files that are being loaded.