How to run Editor in 3.1.0 beta

[Brent_Easton]

Hi Joel,

Is there a way to run the Editor in the current 3.1.0 beta?

Thanks,
Brent.

[uckelman]

Thus spake “Brent Easton”:

Hi Joel,

Is there a way to run the Editor in the current 3.1.0 beta?

Thanks,
Brent.

Yes. You should find VASSALEditor.{sh,bat,exe} in the archive.
If it’s not there, then something went wrong.

–
J.

---

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

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

Thanks Joel,

The ‘-edit’ command argument was what I needed to get it running under the debugger.

I don’t think the Extension handling stuff is quite right. After Editing a module, you can create a new Extension, but the original Edit Module window is left open and you keep editing the module.

The 3.0 work process is that you edit the extension only and module editing is suppressed.

I think it might be asking for trouble to leave the module open for editing once extension editing starts, though the ability to edit multiple extensions simultaneously is interesting. If we go with this, it might be worthwhile adding a Name: field to the ModuleExtension that can be displayed in the ExtensionEditWindow.

Cheers,
Brent.

[Brent_Easton]

Actually, playing with this more, I think

a) The Edit/Create extension options should only be available of the module is unchanged.

b) The Module Edit window should be hidden when the Extension Window opens. The Module Window can be made visible again when the Extension is closed.

Brent.

[uckelman]

Thus spake “Brent Easton”:

Thanks Joel,

The ‘-edit’ command argument was what I needed to get it running under the de
bugger.

Oh, under the debugger. I see, now. (This hasn’t changed, actually. You
would have been able to run the editor directy using -edit before.)

I don’t think the Extension handling stuff is quite right. After Editing a mo
dule, you can create a new Extension, but the original Edit Module window is
left open and you keep editing the module.

The 3.0 work process is that you edit the extension only and module editing i
s suppressed.

I think it might be asking for trouble to leave the module open for editing o
nce extension editing starts, though the ability to edit multiple extensions
simultaneously is interesting. If we go with this, it might be worthwhile add
ing a Name: field to the ModuleExtension that can be displayed in the Extensi
onEditWindow.

Cheers,
Brent.

I was rather expecting that this wouldn’t work quite right, as I’ve
never fully understood how it’s supposed to work.

Do you want to try fixing this or should I?

–
J.

---

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

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

Do you want to try fixing this or should I?

Ok, am working on it now.

Brent.

---

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)

[rk1]

I think it might be asking for trouble to leave the module open for editing once extension editing starts

Because of the way VASSAL identifies where to insert extension components, it’s a big problem if you’re editing the module at the same time as the extension. There will be many bugs if you allow editing both simultaneously.

rk

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

Because of the way VASSAL identifies where to insert extension components, it’s a big problem if you’re editing the module at the same time as the extension. There will be many bugs if you allow editing both simultaneously.

Yes, I fixed that first up.

I’ve got started on this, but it is a bigger job than I thought. I’m also tied up trying to get a large module update out the door. It’s going to take me a while.

Brent.