Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

manager = new Manager(this, graphics, "Default", true); don't work #4

Closed
the-morpher opened this issue Sep 13, 2013 · 2 comments
Closed

Comments

@the-morpher
Copy link

hello,
im realy happy to see the neoforce has been supported again, i think about converting my application to use this one it give more things.

so when i just want to make a test, i can't run my application cause this line crash :

manager = new Manager(this, graphics, "Default", true);

it say that the manager constructor doesn't take 4 arguments.
so i have to use it that way :

manager = new Manager(this, graphics, "Default");

but in the tutorial you said that :

/ Create an instance of manager using Default skin. We set the fourth parameter to true,
// so the instance of manager is registered as an XNA game component and methods
// like Initialize(), Update() and Draw() are called automatically in the game loop.
// If you set this parameter to false, you have to call Manager.Initialize(),
// Manager.Update() and Manager.Draw() manually in their respective overriden methods
// of the game class.
// If you use two-parameter constructor, Default skin is used and manager is registered.
manager = new Manager(this, graphics, "Default", true);

i think it's a usefull that 4th argument as i don't need to type manager.initialize() manager.update() ...
so does it work or not ?

"by taking support of neoforce you have done a good job, keep going"

@Grimston
Copy link
Contributor

Hi the-morpher,

Firstly thanks, I found neoforce to be extremely useful.

The example used to work on the old 3.1 version.  I must remember to update that as it will not work correctly with xna 4

The reason for dropping support for that constructor is you will get whats sometime called the "purple flash of death".

Its actually the back buffer being displayed. 

You should actually call (typing on my phone so if I make a mistake dont hold that against me :p)

manager.BeginDraw(gameTime);
Graphics.Clear(Color.Black); //or another color
//your drawing code

manager.EndDraw();

That should avoid the purple flashes on ui updates.

-------- Original message --------
From: the-morpher notifications@github.com
Date: 13/09/2013 4:57 PM (GMT+08:00)
To: NeoforceControls/XNA XNA@noreply.github.com
Subject: [XNA] manager = new Manager(this, graphics, "Default", true); don't work (#4)

hello,
im realy happy to see the neoforce has been supported again, i think about converting my application to use this one it give more things.

so when i just want to make a test, i can't run my application cause this line crash :

manager = new Manager(this, graphics, "Default", true);

it say that the manager constructor doesn't take 4 arguments.
so i have to use it that way :

manager = new Manager(this, graphics, "Default");

but in the tutorial you said that :

/ Create an instance of manager using Default skin. We set the fourth parameter to true,
// so the instance of manager is registered as an XNA game component and methods
// like Initialize(), Update() and Draw() are called automatically in the game loop.
// If you set this parameter to false, you have to call Manager.Initialize(),
// Manager.Update() and Manager.Draw() manually in their respective overriden methods
// of the game class.
// If you use two-parameter constructor, Default skin is used and manager is registered.
manager = new Manager(this, graphics, "Default", true);

i think it's a usefull that 4th argument as i don't need to type manager.initialize() manager.update() ...
so does it work or not ?

"by taking support of neoforce you have done a good job, keep going"


Reply to this email directly or view it on GitHub.

@the-morpher
Copy link
Author

Thanx Grimston to answer me that fast,
ok, i'll keep implementing this;

i've posted another question as it's another issue i've found before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants