Got this kind of crash when browing in amiga.org portal (when scrolling the forum page)
Quote:
Crash log for task "Odyssey" Generated by GrimReaper 53.19 Crash occured in module graphics.library.kmod at address 0x019AF38C Type of crash: DSI (Data Storage Interrupt) exception Alert number: 0x80000003
tried to access AmiStore and pay with PayPal. As before with the donate buttons, Odyssey (original 1.23 and r5-beta05) doesn't seem to be able to pass the Recaptcha phase. Any ideas how to proceed?
I fear no solution. Its probabaly the same as why google's capcha stop working : those modern popular sites start to use more newer web things, and without updating of core we can do nothing.
Of course, there can be some way like take some site where capcha not works, then debug it till death to understand what it use exacly and why it fail (i.e. what it miss in webcore), and then try to add only that part from today's webkit. But i not sure anyone there want to sped their time on fixing "site by site" :)
I leave you a short video, sorry for the video, but many times they are easier to better explain ideas. I don't know Odyssey well and I have to work on it even if it's a simple browser I hope the steps are right to explain what I mean.
separate note: I must specify that adding the line directly in the user-startup the browser slows down a lot. While if I use spoffing directly in Odyssey preferences this does not happen.
I don't need to activate the "composite" in PREFS / GUI
Since beta06, there will be no needs to enable "composite" in prefs:gui, all works even if you had it disabled. But works only on cards which support compositing. Winuae does not.
Quote:
nor to use the "YouTube_Fullscreen_Fix.js" script
That script need it only for those ones who have composite video working to change on the fly youtube's inbuild video player on our one, so pressing on fullscreen will start rendering in fullwindow. But only on cards which use compositing. Winuae are not.
Quote:
I can activate the full screen view with the appropriate "box" and then put the video in full screen.
Without compositing, and without youtube_fullscreen script, you just use inbuild fullscreen (fullwindow) resizing done for some browsers (like one you mimic with your user agents).
Of course it will be slow on your side as:
1). you don't have compositing based card (or any patch to make use of it over winuae) 2). without youtube_fullscreenfix script and playing with user-agents all you can have its fullscreen which in real resized window , which make things be even slower as default, non resized, window mode.
Quote:
I must specify that adding the line directly in the user-startup the browser slows down a lot. While if I use spoffing directly in Odyssey preferences this does not happen.
That mean there different spoofing string in compare with your one in startup script, and one we use in browser, and with your one probabaly sites you visit start to choice some other way of rendering which is slower. Expectually if you use big stuff like youtube and co.
Quote:
I wanted to ask if it could be included in the spoffing of the next versions
What one exactly, that one:
Quote:
Mozilla / 5.0 (Linux; Android 7.0; SM-A310F Build / NRD90M) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 55.0.2883.91 Mobile Safari / 537.36 OPR / 42.7.2246.114996
Or that one :
Quote:
Mozilla / 5.0 (Linux; Android 9.0; G901F Build / KOT49H) AppleWebKit / 537.36 (KHTML, like Gecko) Version / 4.0 Chrome / 30.0.0.0 Mobile Safari / 537.36
Hi kas1e, Thank you for answering me and explaining many things to me I have been fond of amiga since I was a boy as I said I am aware of the limits of winuae, me is the only way to use Amiga for me. I made many changes to make it pleasant to use.
I did a lot of tests before asking you for spoffing if it can possibly be included in the next version of Odyssey.
This is what works very well and is also compatible with external links that refer to youtube and also with the main youtube page.
user-agent: "Mozilla / 5.0 (iPhone; CPU iPhone OS 12_4 like Mac OS X) AppleWebKit / 605.1.15 (KHTML, like Gecko) Mobile / 15E148 KAKAOTALK 8.7.8"
turns out to be the fastest and also a lot, and compatible with everything else. Much better than "Android 7" or above.
Thanks again if you decide to include it, I really appreciate the work and time you are dedicating to this project.
I leave you a short video i just installed the software enhancers i still have to configure everything especially the audio. Keep in mind that the real speed is also limited by the software video capture program. Thanks again, as soon as I have the opportunity I will make you a small donation for your work. Why these projects must be supported. They take time and work on your part.
I did a new test with Odyssey 05 "full screen" using MUI and I'm very happy, I used the spoffing listed above: "Mozilla / 5.0 (iPhone; CPU iPhone OS 12_4 like Mac OS X) AppleWebKit / 605.1.15 (KHTML, like Gecko) Mobile / 15E148 KAKAOTALK 8.7.8" I don't have a graphics card but it works very well. I'd just like to ask: how do I move the screen that I promote via MUI options.
In practice the screen of MUI remains fixed, instead I would like to have the possibility to move it like any window.
I have done many tests but I cannot do it. Thanks and sorry if my question is "OT" Thanks again to everyone. here the video if it can be useful to better explain my request https://www.youtube.com/watch?v=VvrL5nUYtxI
It took me quite a while to discover what you are trying to show. Perhaps you should describer the problem a bit more instead taking videos of several minutes including the boot process, although the interesting part comes towards the end and one has to guess what might be wrong.
If I understand your video right, then at one point the Odyssey window is on the Workbench screen and no matter how often you try to jump the the "Odyssey" screen it still remains on the Workbench screen. Only explicitly choosing "Workbench" first and "Odyssey" afterwards makes it jump to the desired screen. Is that correct?
@tboeckel Hi, Thank you very much infinitely, I will try as you told me to do. And thank you for your interest and your answer.
@kas1e I know it can be boring, but my English isn't perfect. here I put a video without the use of a video capture program And that's why I'm happy with these new updates of Odyssey, I used a mobile phone at least you see the real speed of Odyssey with Youtube. As soon as I leave home these days, I will make a donation https://www.youtube.com/watch?v=f6rLxMTnfOw
Then did you re-converted the translation files to obtain back the .ct files we need for all translations ? I have updated my italian owb.ct yesterday night, you may create a new translation folder in the github repo, so we can put all translation files there
@samo I just added new thing on bottom, and fix the older strings on the place where they were. Its just seems indeed too much hassle at the moment to do it like i want before, and to be honest i never liked all those translations and spending that much time on. Besides knowing amiga users i am sure if i will add it as i wish (in the middle, increase versions, so no old catalogs will be used, doing it all on my side, etc, etc) there will be issues and reports about.
So at least for now there will be just updated OWB.cd and everyone can translate what and when they wish :) Maybe for some final version when it will be about going to os4depot like 1.24 or something, we can resturcutre it all, and create all new CTs and increse numbers etc, but for now it just as it was : updated OWB.cd
Yep. i update my translation according to the very latest owb.cd you update recently in github
Quote:
I just added new thing on bottom, and fix the older strings on the place where they were.
That's ok, imho there is no need to place strings in a perfect order, putting new one below is more than enough
Quote:
So at least for now there will be just updated OWB.cd and everyone can translate what and when they wish :)
Sure, but putting all that .ct files directly in repo will be better for sure, so all files will be quickly availible for any old and eventual new translators All you need is use the tool to revert back the owb.ct files we currently miss, then create a new translation folder in repo:
Translations --> put all owb.ct files for various languages here
Sure, but putting all that .ct files directly in repo will be better for sure, so all files will be quickly availible for any old and eventual new translators All you need is use the tool to revert back the owb.ct files we currently miss, then create a new translation folder in repo:
Translations --> put all owb.ct files for various languages here
Yeah, just later a bit. As it still take time. Because recreating .ct files from translations weren't that perfect via simplecat, it give some warnings which manually need to be deal on. Nothing important or problematic, just need to spend some time on.
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
