Odyssey 1.23 progress: r5 RC2

@Fab

Ok thanks for confirmation, so in that case what gadget/s need to be displayed when in fullscreen mode ?
Only the depth gadget ?

P.S
Aniway did you have any sort of spam filter in your public mail address ?
Lately I sent you a couple of mails but you never replayed :)

@kas1e

Thanks again for your efforts to get the latest Odyssey working on OS4.1!

How close are you to having a public Beta?


Scott

@ScottCabit
Quote:

To summorize:

1). need to add native pointers (easy)
2). need to add support of all those different languages as done in 1.16 (now easy as well)
3). need to adapt few bits there and there
4). there some moment with clipboard hook: to make it works on os4 we should run it from the same process as owb (because of newlib and stuff) , so, some flags and stuff added, as well as another bunch of different includes, all of this also easy, just need to sort a bit includes which i had to include.

Then, after that, it can be released, but it will have 2 major problems as i see it:

1. Video player only in window mode => slow. It will need time to make overlay support for cards with ovelay, and that compositing based hw acceleration for new radeonhd cards. I think, 1.23 can be released just with window mode at moment, as it all can take time 100%.

2. After all my tests, i found, that aos4 ports, crashes on some sites, on which the same morphos versions didn't crashes (i.e. those crashlogs related to timing or something). Joerg says before for me that he have the same issues with his old OWB , and i should use his timing code. And i tried to use it, but bugs the same. On which he says, that he fix as well something in webkit, to make it works. In end which leads to point that in all previous ports, and in current 1.23, there some timing issue exactly on os4, with which need to deal to make it 100% the same as on mos.

That bug happens from time to time, but i currently didn't spend many time on it, but that issue #2 about which need to think before release: i.e. release it like this, or waiting till i with help of others will not fix it. Of course even like this 1.23 is less crashy and much better than 1.16, but i want to make now everything good, so no one will blame me for all my effort later. I don't know if Joerg will in interest to help this time, but will try to ask him about help on that issue (at least his help with curl and typing in different languages was fast enough and good).

@Fab
Quote:

If speed in window mode only about cairo, then maybe that latest cairo 1.12.16 somehow slower than one you use currently ? I use it with pthreads, not with semaphores, but i do not think it can make such a %30 difference in playback..

@all
Quote:
That one done

@kas1e

Don't forget the latest italian catalog i sent you via PM

About your point 1 (mouse pointers)
.. so also about the autoscroll button of which we talked here:

http://www.amigans.net/modules/xforum ... t_id=87067#forumpost87067

How about using the autoscroll button from the Joerg version of OWB ?

@samo
Quote:

I already (from very first port) use Joerg's code for mouse pointers. And i just checked 1.9, 1.16 and there is wasn't any cursors for autoscroll, while functionality works, there is no images for auto-scroll at all was, so i didn't forget it, it just didn't works at all before.

Quote:

Sure, its all that easy :) Now only need to find out where the code related to it, and why it didn't works before, and how to make it works :)

EDIT: did autoscroll image works in joerg's owb ? If so, how can i check it ?

@kas1e

Yep sorry i talk easy but i know that easy things doesn't exists at all..

But at some point I also got it to crash in some way -->

http://bugs.os4depot.net/index.php?function=viewissue&issueid=874

Quote:

Yes it works perfectly on the Joerg version, just do that:

1 - Open OWB and load a long webpage (a page that add a scroller, for example the amigans.net page you are reading now!)

2 - Click the middle button of your mouse

3 - Just move your mouse (any direction is possible)

@samo
What messy about odyssey ? You just dbl-click by midle-mouse, and then by moving mouse up/down its all auto-scrolls. When you want to disable it, you press midle-mouse button again, and all works.

As for crash, it looks like something about dragging in mui, but, as you for sure know, no step-to-reproduce, nothing can be done. If you want to fix that crash, try to reproduce it step by step.

Also i tried now joerg's owb: i just go to amigans, press middle mouse button, and no auto-scroll cursor appears and no functionality of need it kind. Instead it just bring me menu with "back/forward/reload".

@kas1e

Ahh ok it need 2 middle click then !

The Joerg version need 1 simple click only .. that why it was strange for me

Quote:

Read my previews post ..

Quote:

Ok will check ..

@samo79
Quote:

I do not know what kind of problems you have, but its all works and in 1.16 and in 1.23, i just tested it myself 100 times now. To make it works you do DBL-CLICK, not single click as in Jorg's owb.


Quote:

What about then read my previous post ? I told you that by pressing on middle mouse button in joerg's owb i didn't have auto-scroll , but menu instead. And i already sort why , there is tooltype about it.

And now after i enable tooltype for, it works _exactly_ the same as in odyssey by logic. There is nothing messy. Differences is that in odyssey you need press dbl-click , not single click. And that currently there is no image indicated that autoscroll enables.

@kas1e

Quote:

Mate forget .. i've edited that post ..
I didn't realized that Odyssey needed 2 click .. all the browsers i ever used need 1 click only for scroll .. that's why the confusion

Quote:

Ok that's fine then, forgot it
I hope you can backport such graphical buttons ..

@samo
Quote:

Already found place for. For 1.16 it didn't works because i just purely comment settings of autoscroll pointer and forget about as never use it:



For 1.9 i do not remember if there was that auto-scroll stuff at all or not. So now just need make that :
SetWindowPointer(_window(obj), WA_Pointer, POINTERTYPE_MOVE, TAG_DONE); works, as there is no POINTERTYPE_* in os4, so need a bit of time for checking joerg's code and co

@kas1e

Quote:

Not in 1.9, according to the Odyssey readme the feature was introduced starting from 1.15 release

Quote:

Ok, thank you to look at

@samo
Quote:
Native pointers code added, now just few mins to fix auto-scroll one

@kas1e

Progress...! Not long now?

@samo79

Aehh, it's more than that. With odyssey you have two autoscroll modes...


With a single mmb click you have autoscroll in the webview, as long as mmb is pressed.

With double mmb click you have autoscroll in the webview, without the need to keep the button pressed.

@kas1e

There is no need to call SetWindowPointer() anymore to set one of the internal pointers. set(window, MUIA_Window_PointerType, type) works perfectly. Check the SDK directory that is coming with the MUI releases. Depending on the possible directions a value like MUIV_PointerType_NorthEastSouthWestResize should be exactly what you are looking for. MUI4/AmigaOS4 has some additional pointer types compared to MUI4/MorphOS (see NewStuff demo).

@Thore
Yep, thanks a bunch, as i says in mails it works!

@Fab
Seems i may found some issue in 1.23 (mos version): when you enable auto-scroll, and then move mouse a lot outside of the main window, then at some point, mouse pointer change state on "normal" one, while auto-scroll feature still in the work. It through pretty hard to reproduce, as for some time at just go at amigans, dbl-click mmb, move few times like madman over screen (include odyssey window and outside area, where cursor change the state) and bug is here. But another times trying hard to reproduce and can't.

Or another case, like right now i write that post on mos version, press for autoscroll, then move mouse inside of odyssey a lot, and at some point cursor start to be like showing me "i can type things", while autoscroll still enabled.

@kas1e

/Off thread
i read in this very thread that you compiled cairo 1.12.
Could this version be used instead of the old version that comes with the SDK?