As for the freezing in the pathstroke demo: The crash at the beginning is because a wrong setting in the icon info. It has been solved in the release on os4depot.
As for the crash after 1-2 minute: Have you by any chance tried to enable the opengl button? Because that is dangerous (sorry forgot to mention that)!
:)) Will try to compile today just my previous stuff : hexglass, easypaint and colorcode to see how fast it works now. And then ..
But remember, for the race: only quality stuff ! Not something very easy. And only those which will works fast over all native settings enabled :) I already prepare some tasty links.
Know how many sobjs QT is used, how hard code of QT itself is, how we all the time know that we can't go futher than some begining steps, there is opposite: 2 qt apps at one time !
And its even not ultra-slow. Pretty surprising that it even runs (because is's a looot of sobjes, and they all placed in the memory twice, because sobjes not shared on os4). I.e. from techical poin of view, its really nice progress.
I tryed to recompile EasyPaint (with new SDK/new QT of course), and sadly to say it have new problems there and there.
For first, now with opegl (i.e. as it was before) rendering, it just kind of overlap some texture over another one, as well as mouse cursor seems to be wrong because of the same problems (about -20/-20 by x/y).
There is screenshot of opengl rendering when you run it. And There is screenshot of opengl rendering when you just close a tab (so it show that its opened tab overlap everything). Like some chords bug or kind.
The other major problems is that with native-painting its just produce total mess. Have a look at at screenshot of native painting
There you can get archive with source/binary of EasyPaint. Its very-very small one, so will be good to find out and fix bugs in QT.
PS. Also found that with NativeDialogs OpenFile do not works.
@samo79 You not need to run it, as its not works (see screens). Its just test archive for alfkil (which i should send via mail of course). But just in case: qt => stack size if have crashes at run.
@alfkil Sorry to say, but somehow I find the new native Font/Rendering Version not that mucht faster compared to what we had before. This is on SAM440 mini@667 / onboard gfx. However it might show it strength, when it comes to longer text scrolling etc.
here is a bug When using the textedit example with native fonts you can not see "bold" text, even if you marked it and chose "B" in the Toolbar. Probably it's not even a bug, it is probably how AmigaOS handles fonts.
What so ever, still great work, and really appriciated - BIG THANKS. Wondering how hard it is to code a basic wordprocessor (lets say with the capabilities of FinalWriter or Word 97) ?
Thanks for all the reports, I think it shows very well how alive the amiga community is (compared to how small we are .
Now, I was fearing something like this would happen (= one big mess of all different sorts of problems), which is why I took so long with this release in the first place... I am too tired to look into it all tonight, but tomorrow is a new day . Keep your faith!
Thanks again, and nightie-night.
PS: Obviously, not having libming.so in the flasQ archive is my mistake .
Now, I was fearing something like this would happen (= one big mess of all different sorts of problems),
What is really suck, its when you think that "now i will made everything perfect, without any single problem!" , spend a lot of time on it, when uploading you _sure_ that all will be good, and then common ! Any kind of problems coming , which just should't :)
To positive side, i notice that when i run EasyPaint in native painting, somehow manage to see how i draw something somethere , its visibly that drawing are faster than opengl ones.
Seems just some mess with x/y somethere + maybe not fully up2date SDK (maybe forget to update some includes, or some libs, and so it produce such stuff).
Naa i think it's quite normal for a huge project like that, it's a step by step job and i will surprised if all goes well at the first turn, each release is better than the old and this is the most important thing .. but some new problem may always happen and then need to be fixed again and again, then other cool things will be improved/added and other worse issue come again and so on ..
At the end all of that need a lot of time and resource on both you and betatesters ... but we are here to help aniway and we have also a lot of free time to spend
Out of curiosity do you ever looked at the new QT 4.8 platform abstraction layer?
I'm not really a programmer but from I could read, this should be some sort of way to overcome differences on how the host operating system renders QT apps.
...it allows porting Qt to different windowing systems and devices easier. It provides a clean abstraction layer for porting QtGui to new window systems....
I think I spotted the bug in EasyPaint. It uses QImage, and QAmigaPaintEngine::drawImage() doesn't take care of translations. EDIT: Yes, I was right and it is fixed!
The hexglass bug is a little more tricky, I don't think it is the same one. Maybe something with clipping here. EDIT: Actually I was wrong, it was the same issue, and it is now fixed! Yay
@gerograph
It is a known issue, that bold, italic and underline doesn't work. It is just out of pure laziness and will be fixed soon.