Qt 6 progress

@smarkusg

Does the old Qt 4.7 version work for you?
I ask because it's maybe a more mature version than the new one currently in development
Afaik Qt 4.7's compiled software can also be run from both icon and shell

@samo79
I have seen that the version for QT4 has ‘Worbench’ set instead of ‘Shell’.



I haven't checked if QT4 works for me.
I probably did something stupid.
I will try to find a solution later, it is not an urgent topic.

@smarkusg

Quote:

Strange, I did not foresee a problem here. There doesn't seem to be any failing calls in snoopy, so perhaps this is a feature of clib4. I haven't studied this, but maybe there is a special main function, that needs to be implemented?

EDIT: I have a question - did you test the native build tool chain?

@elfpipe

My compilation is cross-compilation not native.

I was reminded that I once encountered a similar problem with one SDL2 frontend to ffmpeg under clib4 under c++
If I find this program and make sure this is the case, I will definitely report the problem on the clib4 github.

@smarkusg

Quote:

Ok.

I have tested a basic clib4 app, and I can see that it produces normal functions but it doesn't produce CON: output. Probably there is some path issue, that prevents the qt app from opening the environment, although I have trouble seeing what that could be. If we could redirect the stdout and stderr output, we could probably see what goes wrong.

@elfpipe

I have quickly rebuilt clib4 with debug enabled.
It looks something like this


this message only appears if I try to run the QT program from icon(workbench)
[DOS] ERROR: WaitPkt() got a message, NOT a DosPacket, - bouncing it.

I will rebuild QT with DEBUG and paste possibly what QT shows
(weekend is coming and I may not have time today - I will paste when I rebuild)

Thanks for your help

It seems stuck in WaitPort(). The funny thing is if you call "avail flush" and then execute the program again from WB it will work..

Edit:
Find the problem.. I'm on it..

Edit2:
Get latest changes

@afxgroup

It works - thank you very much for fixing it

@elfpipe
I have a question about file handling in QT6.
Are you going to use the native AOS4 dialogs for file handling or should file handling be done with Qt?

In order to have the Amiga name displayed in the AOS4 interface, it is simple.
You can change this in qfilesystemmodel.cpp- >QString QFileSystemModelPrivate::displayName(const QModelIndex &index) const
In order for Amiga files to be displayed correctly in qfiledialog.cpp, I had to add code to QT to handle it (similar to Windows). I have tentatively managed to do this, I still need to finish it.
However, I noticed that the native AOS4 file handling windows are faster. I have added the code from QT4 (print to pdf dialog)
I'm asking because I don't really know what your plans are on this topic
here you have a movie test only with the change of ‘displayName’ , test2 with support for AOS4 paths

video -> https://youtu.be/5QH_IK8EX-k

Thanks for your help and guidance

@smarkusg

Short answer : It is the plan, as soon as the native build environment is confirmed and gl rendering is at an acceptable state, that work should be done to update all relevant modules from the changes done in qt4. I am pretty sure, that most could be used in some form, and it would be quite clear where possible upgrades could be done to those changes.

It is nice, that you are doing experiments with various improvements. If it is ok with you, I would love to include those changes in the final version whenever it seems reasonable.

@elfpipe
You are right. It's your project, it's cool that you have a plan as you presented it
I, for now, will leave my expemperiments for my own use.
I won't litter this topic with my posts.
Thank you for your time.

@smarkusg

No-no, I mean if you do a better version than mine, that's perfectly all right with me. I am sure that you are on the right track and that the work you are doing is worthwhile. I am keeping the repository open because of legal reasons, but also just because I like to share. And I don't like to take credit for the work, my contribution compared to the whole is very small. So if you feel like going big, go for it. :)

EDIT: I know the project has been stagnant for a while. I am just glad, that there is some progress.

@smarkusg

I'm not familiar with QT, but it's great what you're doing it could mean we could use a few more apps and programs under AmigaOs4.1. Maybe even QtWeb one day.

As elfpipe mentioned you should continue and share your progress here as long as you enjoy it. Maybe you two can also work together to get the QT Project moving faster.

@elfpipe
There were some cool example videos from you in the thread above

@Maijestro

Thanks, I am glad, you enjoyed them :).

@smarkusg

I can recommend, that you do a shared build instead of static. We did some work to fix some symbol resolutions in elf.library, that didn't work before, so now ui signals will actually reach the callback function. This depends on *beep*.