I don't think these have come up earlier:

1) When a mutli-assign is made during startup (for instance by MUI in the user-startup), and if there are files with the same filename in both directories, then boot will hang on the splash screen. I've had this happen multiple times, and I've had to remove the MUI assigns from user-startup alltogether. This is NOT very userfriendly at all.

2) The discdoctor (or whatever it is called nowadays)! When a program (for instance Quake 3) crashes in the middle of something with files open, then the disc will be unvalidated at reboot and the discdoctor will initiate at boot time. This might _also_ hang up the machine at the splash screen. Even worse, it might not even validate at all unless you reboot without startup-sequence and wait (often for a long time) for the discdoctor to finish. This has been a problem since old classic days, and I think it is time for the discdoctor to a) become verbose and tell the user, what is happening and b) for system boot to wait until the discdoctor finishes before continuing the boot process. Anything less is going to break the user experience.

@Raziel

As I said: I'll see what I can do. Which might not be much, but at least I'll give it a try

@Raziel

Hehe I'll see what I can do once I'm "done" with Qt for Amicygnix.

Any news on the java front?

@abalaban

I finally got around to reply

@DAX

and Google Earth... and Skype... and.... 8-D

@kas1e

...and _create_ many more new apps, hopefully

No seriously, if you are thinking of learning how to code apps, Qt is a really great environment. Of course you have to get your grips on c++, but then you get a really easy and diverse environment, and not to forget near instant portability 8-D

A native version is pretty far out in the future, though...

@kas1e

Thanks for the info

I'll see if I can use it, only rebuilding libQtGui takes almost half a day... :(

First screenshot of the Qt Designer running:

http://dl.dropbox.com/u/5482530/Images/designer.png

And yes, it _does_ work and doesn't crash (at least not yet!).

@Chris

I needed the static version, because Qt cannot build with -use-dynld at this time. Sadly.

There is a bug in elf.library, though, that makes dlopen() crash with my plugins.

@MickJT

Thanks. libdl seems to be exactly what I need!

I'm trying to expand plugin-capabilities of Qt, and
some code refers to dlopen()/dlclose()/dlsym(). The code links, but does not work.

Now I'm trying to make a small test-app that uses
dlopen, but it doesn't link, telling me "undefined reference to
dlopen".

I can't seem to find dlopen as symbol in any of the SDK libraries, so how come Qt links? If there is some macro definition somewhere, I can't find it. Help!

@kas1e + others

I think the big slowdown is some obscure timing issue, because in several
of the demos I can "speed up" animation by moving the mouse in front
of it.

About a native port: It is very unlikely that I will find time and (not least)
energy to do it. Qt is a monster, and the only real reason that I have
come so far, is because of Edgar and amicygnix. I'm going to try and
finish the amicygnix port, and then I hope somebody will be so
inspired, that they dive in and finish the job

@Chris

Maybe update the readme to explain a bit more for us dummies, who don't know how the printer system actually works ... ? :)

@rwo

Hehe, it's working alright, but something is still missing.

I found out, that prefs/Printer was set to Postscript instead of Generic. So far so good. But when printing from Multiview, the printer takes in the paper, and then it just sits there waiting for smth and nothing is printed. Then I try switching back to Postscript, go to a shell and type "echo hello >prt:" and suddenly my text file comes out, followed by the PS mumbo-jumbo from before follower by lots of linefeeds...

So it seems, that when printing generic, the printer is missing a 'flush' or 'eof' at the end of printing. Correct??... Is this an issue of your driver, or is it the software (multiview etc.)?

EDIT: typing "echo hello >prt:" with Generic turned on does nothing. Also "cat file >prt:" does nothing, except add data, that is eventually flushed when switching to PS mode.

EDITEDIT: Hurrah! I got it printing graphics from amipdf, just needed to install generic HP Deskjet driver from SYS:Storage/printers. Ren?, you are a genius!

@rwo

How do I get hold of the debug buffer? I don't have any serial terminal, if that's what you are talking about...

EDIT: I can tell you, that from amipdf the following text is written by the printer:

%!PS-Adobe-3.0
%%DocumentMedia: letter 612 792 0 () ()
%%EndComments
% The line abo

(each line starting horizontally at the point where the above line ended)...and then comes a lot of (6-7) page feeds, and the printer seems to be left waiting for more data.

Project started at qt.gitorious:

http://gitorious.org/qt-for-amicygnix-amiga-os-4-1

Also updates of SDK and examples uploaded to os4depot (now without debug data ).


Things to be done next:
jpg support doesn't work
there is a timing issue, so animations are slooow
(+more)

I have a HP Photosmart C3180, and I think it is supposed to be DOT4 compatible, but I'm not sure. Anyway, it doesn't work with the usbdot4.device, it only spews out nonsense when I try printing from notepad or amipdf. Does anywone know if this printer is supposed to work with the device?

@alfkil

Alas, I was wrong again: Update 2 _did_ solve the problem, the file dialog problem was just an entirely different issue. Now Qt works with both dock widgets and file dialogs :) (update uploaded soon).

@Mrodfr

I installed update 2, and it didn't solve the issue. Sadly :-I