|
From: SourceForge.net <no...@so...> - 2004-11-27 03:37:29
|
Bugs item #1021568, was opened at 2004-09-02 21:10 Message generated for change (Comment added) made by tmilam You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384719&aid=1021568&group_id=25576 Category: None Group: None >Status: Deleted >Resolution: Works For Me Priority: 7 Submitted By: Paul W. King (kingpaul) Assigned to: Tod Milam (tmilam) Summary: [5.7.4] Creating Custom items Initial Comment: Per http://groups.yahoo.com/group/pcgen/message/79051 I get this error intermitantly also. I reported a couple of weeks ago. It may have something to do with the lst files you're loading. I couldn't duplicate it with only RSRD loaded. --- In pc...@ya..., "Paul Grosse" <paul.grosse@m...> wrote: > I'm getting a bug when creating custom items using > 574 release Load RSRD, create new char, go to inv > tab, click on any item, right click Create custom item, > and then rename it to blah, then it puts the old name > in the Sprop, so I go into the Spop dialog hit delete, > and hit ok. It gives me the following error in a pop-up > and in the DOS box. It then also brings up that same > error every time after that I select Create Custom > Item, until PCGen is restarted. It also happens > anytime I hit the SPROP button and then okay, not > just when I change the name. > > Pop-up message > Error: Exception type:java.util.NoSuchElementException > Message:null > > DOS box error === Paul W. King TM SB, OGL/PL Chimp, Data Tamarin, BoD ---------------------------------------------------------------------- >Comment By: Tod Milam (tmilam) Date: 2004-11-26 21:37 Message: Logged In: YES user_id=777206 I was able to duplicate the error using Paul G.'s steps in 5.7.4. Using the same steps I was not able to reproduce it using the current CVS code. ---------------------------------------------------------------------- Comment By: Frugal (frugal) Date: 2004-11-21 05:33 Message: Logged In: YES user_id=4807 Without knowing which LST files are causing this problem it will be impossible to track it down. Can we please have some details of the LST files that are in use when the problem occurs so that we can replicate it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384719&aid=1021568&group_id=25576 |