Aradiel
November 2, 2008, 12:40pm
1
Hello,
In a module I’m working on, when I edit it with the latest build, the editor replaces all prototype traits used to define a unit by the individual traits contained in the prototype traits. I checked the content of the buildfile and the units are not defined using individual traits but the prototypes I used. This means that it’s the editor that develops and shows the component traits.
I don’t how long it has been so but that’s a pain.
In 3.0.17, it works fine.
In build 4304 it works fine.
This is a bug with my fix merged into 4371. Prototypes are being expanded when editing. I am looking into it now.
B.
*********** REPLY SEPARATOR ***********
On 2/11/2008 at 4:40 AM Aradiel wrote:
Hello,
In a module I’m working on, when I edit it with the latest build, the
editor replaces all prototype traits used to define a unit by the
individual traits contained in the prototype traits. I checked the content
of the buildfile and the units are not defined using individual traits but
the prototypes I used. This means that it’s the editor that develops and
shows the component traits.
I don’t how long it has been so but that’s a pain.
In 3.0.17, it works fine.
In build 4304 it works fine.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com )
Joel,
swampwallaby-work@4373 fixes my last fix. The PieceSlot is only expanded for display purposes.
B.
*********** REPLY SEPARATOR ***********
On 3/11/2008 at 7:41 AM Brent Easton wrote:
This is a bug with my fix merged into 4371. Prototypes are being expanded
when editing. I am looking into it now.
B.
*********** REPLY SEPARATOR ***********
On 2/11/2008 at 4:40 AM Aradiel wrote:
Hello,
In a module I’m working on, when I edit it with the latest build, the
editor replaces all prototype traits used to define a unit by the
individual traits contained in the prototype traits. I checked the content
of the buildfile and the units are not defined using individual traits but
the prototypes I used. This means that it’s the editor that develops and
shows the component traits.
I don’t how long it has been so but that’s a pain.
In 3.0.17, it works fine.
In build 4304 it works fine.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com )
Thus spake “Brent Easton”:
Merged to trunk@4374.
I also replaced all of the calls to getSize().width and getSize().height
with a single call to getSize(), so that we’re not creating tons of
Dimension objects needlessly.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com )
Thus spake “Aradiel”:
Hello,
In a module I’m working on, when I edit it with the latest build, the editor
replaces all prototype traits used to define a unit by the individual traits
contained in the prototype traits. I checked the content of the buildfile and
the units are not defined using individual traits but the prototypes I used.
This means that it’s the editor that develops and shows the component traits
.
I don’t how long it has been so but that’s a pain.
In 3.0.17, it works fine.
In build 4304 it works fine.
Try svn4376.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com )