@samo No. I forward that to deadwood , so he can fix it in main branch, from where i can just copy+paste it. Dunno if he do so, or if he recieve mail about.
@kas1e Somehow I had missed all your work until today! How could that be? I wonder if there was one of those wotchamacallits (donation links) when you started, and did I contribute?
Anyway, it is already my Odyssey, with the one I've been using hidden behind a name change, just in case.
I was hoping for a version that didn't have my gmail website warning me that I need to update my browser because they won't be supporting the one I'm using in the future, but I can live with that.
So a very belated thank-you for your tremendous efforts!
-- backported deadwood's fixes from 1.25: - fixed major memory leak where Frames were not released together with their JS data - memory no longer continuously consumed while browsing - fixed a number of small memory leaks - fix for cookies, which make login to youtube, blogger and some others works again. -- build against newer libssl 1.0.1q (solved Heardbleed issues, as well as give ability to use some https sites again) -- fixed proxy server settings (thanks Thore): str_proxyusername and str_proxypassword get the same ID before, and settings applied to two object with different tasks -- updated codesets.library to 6.19
If all ok, i will upload that one on os4depot. Thanks
Thanks Roman, will test the new version and i will report back ... Aniway with the latest beta i'm using i noted a very strange issue with the (top) menu ..
Sometimes when i browse the web the color of the top-menu will be changed for no reason ... sometimes they become orange, other time blue .. ??
I don't know how to reproduce the issue but it's really strange I never had any problem with the stable version on OS4Depot so probably it could be a recent issue introduced in one of those betas
@kas1e The Odyssey executable seems to be identical to the "beta v7" released back in January (or whenever it was), although the file date is newer. So I guess it was recompiled, but there are no actual source code changes?
I would suggest updating "curl-ca-bundle.crt" to the latest version downloadable from: http://curl.haxx.se/ca/cacert.pem (And maybe use Curl to make that part of your release build script?!?)
@pseudaxos I would be very surprised if Mega Download works at all on an Amiga, given it fully "downloads" to memory (RAM), before it lets you write the download to hard disk.
@sundown I have no idea what versions you were comparing against, but I can assure you I did a binary comparison against the last Odyssey beta version I had (file date 19th January), and it was identical. Kas1e also confirms that it should have been the same, since it was a copy.
@ChrisH I didn't strip it by default because of reassons on which LiveForIt pointed out. Striping will make debug logs useless, as then will have no references to name of functions and so on.
My router developer updated it's firmware and now i can't access the routers webpages anymore and only get this message: Quote:
Willkommen bei Ihrer FRITZ!Box
Die FRITZ!Box-Benutzeroberfläche nutzt moderne Methoden für eine optimale Darstellung auf einer Vielzahl von Geräten. Leider unterstützt Ihr Browser diese Methoden nicht.
Wir empfehlen daher die Aktualisierung des vorhandenen oder die Verwendung eines anderen Browsers.
Mögliche Browser-Alternativen finden Sie hier
Translation: Quote:
Welcome...
The ...GUI uses modern methods for optimized display on a variety of machines. Unfortunately your browser doesn't support these methods.
We recommend updating your browser or using another one.
Unfortunately none of the three (on AmigaOS) available browsers support the new methods.
I checked on a windows machine and the method where it breaks seem to be Window.requestAnimationFrame().
According to to this site the version of WebKit introducing this method was 6.0 (On the linked site scroll down to "Browser compatibility").
Would it be possible to update Odyssey to WebKit 6.0?
Yes but that makes any debug logs from users useless.
While I hate to disagree with you & Kas1e, it certainly does NOT make debug logs useless! You just need to keep the UNstripped executable around (along with the source files that you'd keep anyway), and then you can use addr2line on that unstripped executable, and it will give you the correct information (including function name).
OTOH, yes, having to use addr2line to see function names does make it a little more laborious.
ANYWAY, I never said you should strip Odyssey executable. I merely pointed out that it was not stripped, in case this was an accident. 60MB vs 50MB is hardly worth much worrying!
While I hate to disagree with you & Kas1e, it certainly does NOT make debug logs useless! You just need to keep the UNstripped executable around (along with the source files that you'd keep anyway), and then you can use addr2line on that unstripped executable, and it will give you the correct information (including function name).
News feed
OS4 Feedback forum
OS4Depot Feedback 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
