According to this list AmiUpdate is still at v2.45.
But according to my bug item 144 a really annoying bug has been fixed in 2.46 and i wonder why the release is held back? I'd love to have the bug fixed...any chances for a release soon(ish)?
Quote:
...
Comment added by Rigo on Sun 20-May-2018 20:23:13 (GMT) ---------------------------------------------------------------------
Somehow I missed this bug, and was able to reproduce it. It is now fixed for version 2.46.
Not if it's part of a bigger package (i.e. AmigaOS4.2) with a reasonable price.
If it's one of many (i.e. AmiUpdate, NGFS, GfxDriver, SoundDriver etc.) where i a) have to pay for every single one and b) have to chose to either pay the bills or to have a stable system, i'll drop the unimportant stuff and go with the bills.
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
To be honest, it's been a long time since I looked at that code, so I have no idea why it didn't get released. Perhaps I'll find some time over xmas...
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
edit: btw, can some formatting be done to make the "information" text on an update not being displayed one after the other with no newline feeds? It makes the info very hard to read and looks plain wrong too. (i.e. the MUI updates normally feature a big changelog)
btw, can some formatting be done to make the "information" text on an update not being displayed one after the other with no newline feeds? It makes the info very hard to read and looks plain wrong too. (i.e. the MUI updates normally feature a big changelog)
You ideally need to speak to the author, as it is they that upload those texts.
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
Hmm, i have used a changelog myself for scummvm in the past which is displayed fine in a text editor and os4depot.net but will always lose all new line chars when displayed in AmiUpdates info window, hence I asked for the correct formatting.
What do I need to do to make at least the new line work?
btw, can some formatting be done to make the "information" text on an update not being displayed one after the other with no newline feeds? It makes the info very hard to read and looks plain wrong too.
Rigo: Quote:
You ideally need to speak to the author, as it is they that upload those texts.
please check bug #133 in the amiupdate bugtracker.
@Rigo Can't it be an issue on the amiupdate side to just handle only one way of carriage returns (like 0x0a or something), while there can be 0x0a, 0x0d, 0x0a0d and 0x0d0a
Looks like the server side scripting was stripping out characters instead of encoding them, so the Info window should now show the descriptive text the way it was intended.
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
I just updated to 2.46 and I immediately get a Guru Meditation error:
Guru Mediatation 80000003 Task 0x3de28830 ("Amiupdate") generated an error of type DSI (Data Storage Interrupt) on address 0x1fb2660c Redzone was not damaged Stackpointer inside bounds.
The 'Grim Reaper Debugger' states the the ButtonAnimTask caused the crash. No function name given.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
