MenuManager.getInstance()

[mkiefte]

When MenuManager.getInstance() is called in the ModuleManagerWindow constructor, the instance field is null, which results in an IllegalStateException being thrown. The relevant call is line 151 of VASSAL.launche.ModuleManagerWindow.java.

• M.

[uckelman]

Thus spake “mkiefte”:

When MenuManager.getInstance() is called in the ModuleManagerWindow construct
or, the instance field is null, which results in an IllegalStateException bei
ng thrown. The relevant call is line 151 of VASSAL.launche.ModuleManagerWind
ow.java.

• M.

It’s intentional that an IllegalStateException is thrown when there
is no MenuManager instance, becuase there should be one. But this
doesn’t happen for me.

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

Michael,

You’re probably still using VASSAL.launch.Main as an entry point? I think the correct on is now VASSAL.launch.ModuleManger. Joel?

Brent.

Thus spake “mkiefte”:

When MenuManager.getInstance() is called in the ModuleManagerWindow

construct

or, the instance field is null, which results in an

IllegalStateException bei

ng thrown. The relevant call is line 151 of

VASSAL.launche.ModuleManagerWind

ow.java.

• M.

It’s intentional that an IllegalStateException is thrown when there
is no MenuManager instance, becuase there should be one. But this
doesn’t happen for me.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[uckelman]

Thus spake “Brent Easton”:

Michael,

You’re probably still using VASSAL.launch.Main as an entry point? I think the
correct on is now VASSAL.launch.ModuleManger. Joel?

Brent.

Yes, that’s correct. The only reason Main is still there is so we can
see whether anything was missed during the transition. Once that’s
been done, I think we can remove it entirely.

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[mkiefte]

Yes, that’s correct. Thanks for pointing that out. I only updated from the trunk last night.

But now I’ve got other problems. My debugger is not breaking on ImportAction.performAction and I don’t know why. Certainly, the importer is not working for me, but I can’t figure out why as my debugger refuses to work. Does it work for anyone else?

• M.

2008/4/26 Joel Uckelman <uckelman@nomic.net (uckelman@nomic.net)>:

Thus spake “Brent Easton”:

Michael,

You’re probably still using VASSAL.launch.Main as an entry point? I think the
correct on is now VASSAL.launch.ModuleManger. Joel?

Brent.

Yes, that’s correct. The only reason Main is still there is so we can
see whether anything was missed during the transition. Once that’s
been done, I think we can remove it entirely.

–

J.

Post generated using Mail2Forum (mail2forum.com)

[uckelman]

Thus spake “Michael Kiefte”:

Yes, that’s correct. Thanks for pointing that out. I only updated from the
trunk last night.

But now I’ve got other problems. My debugger is not breaking on
ImportAction.performAction and I don’t know why. Certainly, the importer is
not working for me, but I can’t figure out why as my debugger refuses to
work. Does it work for anyone else?

• M.

The importer works fine for me when I run what’s in trunk@3472.

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[mkiefte]

The importer works fine for me when I run what’s in trunk@3472.

Well that is odd. Remind me to not upgrade the OS again. (Although I was using Ubuntu 6.04…)

• M.

Post generated using Mail2Forum (mail2forum.com)

[uckelman]

Thus spake “Michael Kiefte”:

The importer works fine for me when I run what’s in trunk@3472.

Well that is odd. Remind me to not upgrade the OS again. (Although I was
using Ubuntu 6.04…)

• M.

Try the 3473 build I uploaded just now. This definitely works for me.

nomic.net/~uckelman/tmp/vassal/

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[uckelman]

Thus spake “Michael Kiefte”:

Can someone confirm for me that the importer will actually load an ADC2
module into the editor? Mine is dead in the water and I’m baffled. I’ve
merged the latest revision from the trunk. I’m using java-6-sun-1.6.0.06.
I get nothing. VASSAL just craps out with no exception or error or
anything. java-gcj won’t even start it.

More investigation…

VASSAL is silently printing an errorLog in the VASSAL/ directory. errorLog
attached.

It looks like an exception is being thrown during a call to an exception.
I’m not sure what to make of it. And why is this only happening to me?

• M.

What does ‘which java’ tell you? I think you’ll get the GNU Classpath
java that way, which would be the cause of your problem.

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

Mike,

But now I’ve got other problems. My debugger is not breaking on
ImportAction.performAction and I don’t know why. Certainly, the importer
is not working for me, but I can’t figure out why as my debugger refuses
to work. Does it work for anyone else?

The reason the debugger does not work when editing or playing is because the Module Manager now starts Editing and Playing sessions as a new process that the debugger does not have access to.

To debug the Player or Editor, you have to bypass the Module Manager and create a debug session that starts Vassal.launch.Editor or Vassal.launch.Player directly and set the comamnd line arguments to the pathname of the module.

Brent.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[mkiefte]

Thanks Brent. I’ve almost got it all sorted out. Different Main method, got GCJ and Sun Java to play nice, and different threads to debug. Three separate problems. Rough day. Seems to work fine now.

Is there an elegant solution to the debugger problem or is that it?

• M.

2008/4/26 Brent Easton <b.easton@exemail.com.au (b.easton@exemail.com.au)>:

Mike,

But now I’ve got other problems. My debugger is not breaking on
ImportAction.performAction and I don’t know why. Certainly, the importer
is not working for me, but I can’t figure out why as my debugger refuses
to work. Does it work for anyone else?

The reason the debugger does not work when editing or playing is because the Module Manager now starts Editing and Playing sessions as a new process that the debugger does not have access to.

To debug the Player or Editor, you have to bypass the Module Manager and create a debug session that starts Vassal.launch.Editor or Vassal.launch.Player directly and set the comamnd line arguments to the pathname of the module.

Brent.

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

*********** REPLY SEPARATOR ***********

On 26/04/2008 at 9:08 PM Michael Kiefte wrote:
Thanks Brent. I’ve almost got it all sorted out. Different Main method,
got GCJ and Sun Java to play nice, and different threads to debug. Three
separate problems. Rough day. Seems to work fine now.

Is there an elegant solution to the debugger problem or is that it?

I thought that was elegant

Basically, no, that’s it. When debugging, you need to treat it as three seperate programs - Manager, Editor, Player.

B.

---

Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton@uws.edu.au

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[mkiefte]

Okay, I get it now. I figured out where everything is. Strange, but I’ll go with it. Those times I need the debugger for the importer, I know exactly which file I want to test it on anyway.

• M.

2008/4/26 Brent Easton <b.easton@exemail.com.au (b.easton@exemail.com.au)>:

*********** REPLY SEPARATOR ***********

On 26/04/2008 at 9:08 PM Michael Kiefte wrote:
Thanks Brent. I’ve almost got it all sorted out. Different Main method,
got GCJ and Sun Java to play nice, and different threads to debug. Three
separate problems. Rough day. Seems to work fine now.

Is there an elegant solution to the debugger problem or is that it?

I thought that was elegant

Basically, no, that’s it. When debugging, you need to treat it as three seperate programs - Manager, Editor, Player.

B.

---

Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton@uws.edu.au (b.easton@uws.edu.au)

Post generated using Mail2Forum (mail2forum.com)