eqPump (was VanillaEquipment) keyword
Post MTG Forge Related Programming Questions Here
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
49 posts
• Page 4 of 4 • 1, 2, 3, 4
Re: eqPump (was VanillaEquipment) keyword
by DennisBergkamp » 11 Apr 2010, 17:59
No problems, Jim
I don't think it was just you, I overwrote a bunch of changes as well.

-
DennisBergkamp - AI Programmer
- Posts: 2602
- Joined: 09 Sep 2008, 15:46
- Has thanked: 0 time
- Been thanked: 0 time
Re: eqPump (was VanillaEquipment) keyword
by Chris H. » 11 Apr 2010, 19:12
I checked my notes for the last several months and found just 4 more cards.txt entries to fix. I will move my fixes to the top of the file. We can try it this way for a while and see if it makes it easier on all of us to see the changes. 

-
Chris H. - Forge Moderator
- Posts: 6320
- Joined: 04 Nov 2008, 12:11
- Location: Mac OS X Yosemite
- Has thanked: 644 times
- Been thanked: 643 times
Re: eqPump (was VanillaEquipment) keyword
by Rob Cashwalker » 12 Apr 2010, 03:10
I get <<<< and >>>> all the time in lots of files, including cards.txt and the .classpath. It sucks in .classpath, because it doesn't appear on the tree. It has to be fixed manually.
Eclipse can easily merge differences in the code, but it doesn't handle the cards.txt at all, and manual fixes are prone to these sorts of errors. Maybe a "replace from repository" for cards.txt is better than "update to head". Then paste the new card text at the top and then commit.
Eclipse can easily merge differences in the code, but it doesn't handle the cards.txt at all, and manual fixes are prone to these sorts of errors. Maybe a "replace from repository" for cards.txt is better than "update to head". Then paste the new card text at the top and then commit.
The Force will be with you, Always.
-
Rob Cashwalker - Programmer
- Posts: 2167
- Joined: 09 Sep 2008, 15:09
- Location: New York
- Has thanked: 5 times
- Been thanked: 40 times
Re: eqPump (was VanillaEquipment) keyword
by jim » 12 Apr 2010, 09:48
I agree, that sounds like a better idea. I was also thinking, in terms of your previous suggestion of submitting files separately, that I would submit cards.txt separately from other changes. I'll try doing both these things from now on.Rob Cashwalker wrote:Eclipse can easily merge differences in the code, but it doesn't handle the cards.txt at all, and manual fixes are prone to these sorts of errors. Maybe a "replace from repository" for cards.txt is better than "update to head". Then paste the new card text at the top and then commit.
Ironically, for my next submission I don't have to touch cards.txt anyway.

- jim
- Posts: 46
- Joined: 19 Feb 2010, 01:46
- Location: Sunny New England
- Has thanked: 0 time
- Been thanked: 0 time
49 posts
• Page 4 of 4 • 1, 2, 3, 4
Who is online
Users browsing this forum: No registered users and 12 guests