Null and AppSettings.NULL discrepency/bug?

Now apologies if I have missed something fundamental but…



I am creating a headless server but using the SimpleApplication for ease of use. When setting up a null renderer you use the AppSettings.NULL constant. However, if you want the Audio Renderer to be ignored you have to set the value to null as the check is:



if (settings.getAudioRenderer() != null){

audioRenderer = JmeSystem.newAudioRenderer(settings);

audioRenderer.initialize();



listener = new Listener();

audioRenderer.setListener(listener);

}



I would have thought the NULL constant should be used for all ‘null’ settings for consistency? Like I said, feel free to correct and abuse me if I am just being dumb, it happens…



Matt

Yeh, I agree :slight_smile: But actually now you can set the video renderer by using “null” too :wink: