The display to the consumer should be in a format that it stays noticeable, or will be conveniently retrievable, and doesnt simply adobe flash on the display and vanish.VLC chooses this is definitely not a properly-formed Web address (an problem which I am not quarrelling), and then just quits processing the WPL document without offering the consumer any description at all.
Actually if there are 100 properly-formulated items in the rest of the document, they are ignored. This will be pretty poor treatment of the consumer, and makes it extremely tough for himher to right whatever their problem is. Information: The problem is usually in the DemuxPlaylistwpl.d module, in the readbody function, at line 203. If the return value signifies the users text chain is not an MRL, the Come back statement is usually executed. Control goes by back again to Demux, which rapidly ends, returning control to ImportWPL, which furthermore quickly ends. ![]() What should be performed: In place of the RETURN statement there should become a stop of code that: 1) tells the user that it discovered a issue and obviously details the problem and shows the text message that has been deemed to become in mistake, 2) flushes that stringelementline that it couldnt understand and goes to looking at the following one, 3) continues looping until all outlines in the file are prepared. The actual text message that is usually in error should show up in the playlist, likewise (but not identically) to a correctly-formatted Website address that factors to a non-existent file, with a appropriate error information. This method the user can even more easily locate the item in his playlist that will be in error. NOTE 1: the triggering occasion could become a whole assortment of circumstances, not just the case of relative addressing which uses restricted personas. Take note 2: the module DemuxPlaylistm3u.m does NOT abruptly finish when experienced with the same situation. It furthermore doesnt ell the consumer about the problem - which will end up being covered in a independent bug record It processes all being successful items in the michael3u playlist document. Visualization Key Led - Plugin Do Winamp V2.1 [] Professional Git ProblemDemuxers: Playlist 22533 VLC doesnt show consumer about error in M3U playlist Demuxers: Playlist professional git problem normal new 2019-07-08T22:16:4902:00 2019-07-08T22:16:4902:00 Operating-system: Home windows 10 (most probably happens in some other environments mainly because nicely). Visualization Key Led - Plugin Do Winamp V2.1 [] Series In AnExample of problem: When VLC incurs this series in an M3U playlist. VLC decides this can be not really a properly-formed Link (an issue which I am not arguing), and then just punches it out without providing the user any explanation at all. VLC continues processing the remaining outlines in the document, but pretends this one media specification under no circumstances existed. Effect of issue: When a user provides VLC an Michael3U document with a 100 media products and VLC pretends there are only 95, the user wastes a lot of period figuring out what went wrong. Very first he provides to number out how numerous are lacking (VLC doesnt state how several items in the playlist had been imported, therefore he provides to matter them in the screen). After that he has to body out which types are lacking by aesthetically evaluating his Michael3U file to the playlist screen. Then arrives the really hard part why did VLC disregard this item And the consumer can be off scrounging through tough to discover documentation and checking community forums and posting problems. Why cant VLC simply reveal its details with the consumer in the first place: what consumer text triggered the issue and what will be the issue. Location of problem program code: The problem is usually in the DemuxPlaylistM3U.chemical component, in the ReadDir functionality, at range 301 which is goto mistake. The code has appeared at the return worth from ProcessMRL and made a decision that the customers text will not signify a URLMRL. So it just ignores the users specification and goes to an error stop of program code without educating the user. What should end up being done: Before the goto error; declaration there should become a block of program code that somehow tells the user what portion of text was deemed to become incorrect or unprocessable and why.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |