From: SourceForge.net <no...@so...> - 2010-09-12 02:13:13
|
Patches item #3054536, was opened at 2010-08-28 04:57 Message generated for change (Settings changed) made by fredm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=596650&aid=3054536&group_id=91293 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Accepted Priority: 5 Private: No Submitted By: Sergio Baldovi (sbaldovi) Assigned to: Nobody/Anonymous (nobody) Summary: Loading RZX file with external snapshot Initial Comment: Hello there, I usually use RZX files recorded in competition mode, so there is no an embedded snapshot. I would like to rise two suggestions: 1) Fuse fails to load an RZX without an embedded snapshot from menu (command line works ok). This happens because no snapshot is loaded and the playback starts from the current state. I think it would be better if fuse could autodetect this kind of files and ask user for an external snapshot. fuse.rzx_external.diff file contains an approach. 2) In competition mode Spectaculator adds a snapshot block to the RZX file, linking the external snapshot. Libspectrum ignores it (ok) but raise the error "rzx_read_snapshot: skipping external snapshot" when loading. I think that's not an error, it's an info message. When many files are played it's a bit annoying this message. Is there any purpose or could be removed it? libspectrum.message.diff file contains an approach. Regards, Sergio ---------------------------------------------------------------------- >Comment By: Fredrick Meunier (fredm) Date: 2010-09-12 12:13 Message: Applied in slightly modified form for revision 4157. ---------------------------------------------------------------------- Comment By: Fredrick Meunier (fredm) Date: 2010-09-05 22:11 Message: 1) This sounds reasonable to me, unless I hear a complaint I'll check this in over the next few days 2) Given the behaviour from the patch in 1 I think this makes sense, I'll commit this on the same basis as 1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=596650&aid=3054536&group_id=91293 |