@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

@all:

First of all: Don't get your hopes up too high. A lot of features are working, but a lot is also missing. As you will see, only 4 libraries are available now. QtGui has problems with threads that I have been banging my head against for some time with no success. Basically, if you add any gui element that opens a thread (like a file requester), you are going to get into trouble.

I'm going to work on a different project for some time now, so I wanted to share the project at it's current level. Of course I'm going to work on it again in the future, and of course any help would be appreciated

About the sources:

1) Stay away from the configure script!
2) Use 'gmake staticlib' to build any library, as dynamic linking is not available at this stage

New SDK available:

http://dl.dropbox.com/u/5482530/Qt/qt ... rce-microsdk-4.6.2.tar.gz

It requires amicygnix and the amicygnix SDK.


If you just want to watch, there are a couple of random examples:

http://dl.dropbox.com/u/5482530/Qt/qt ... nix-examples-4.6.2.tar.gz

Examples only requires amicygnix base, no SDK. Please run from Workbench!



And finally, if you are in for the big lebowski, here is my complete source archive:

http://dl.dropbox.com/u/5482530/Qt/qt ... mpletesource-4.6.2.tar.gz

Requires: Patience, lots of patience and spare time...


Happy coding!

@salass00

Yeah, checking printouts is a good idea, and you
happen to be spot on... I must have been asleep
writing it... Doh!

My sources can be downloaded at

http://dl.dropbox.com/u/5482530/gdb.lha

(in a few minutes). I didn't take the time to
organize it, so it is filled with .o files, .svn stuff
and a lot of other crap.

@tonyw:

I was thinking the same thing, that the port was
deleted, but why am I able to receive an actual
message from it a little later on?

@Daedalus

It should return the signal it receives. That is, if it receives SIGBREAKF_CTRL_C, then it returns that, if it receives a signal from the port, it returns a field with just the ports signal bit set. That's how it works in my test app, and that's how the docs describe it. Only place it doesn't work is in GDB. Strange...

@kas1e

I'm just fooling around. I managed to compile it and
fix a bug that made it crash every time it loaded some
code, but apart from that there's not so much progress.

Working on GDB, I discover that IExec->Wait() often returns
-1. The docs say nothing about error conditions, so what could
this possibly mean?

This is the line:

sig = IExec->Wait(SIGBREAKF_CTRL_C|SIGBREAK_CTRL_D|1<<msgport->mp_SigBit);

EDIT: Byt the way, the port _has_ been created, and the sigbit is set.

@joerg

Just saw your response now. Thanks J?rg!

sched_yield() is (afaik) supposed to make the current task/thread
jump to the back of the task list. Is there some way to do/emulate this
with exec or pthreads?

@Framiga

Yup, or rather now I'm running 16-bit with no shadows, no problems as they say. Bit of a shame, though.

EDIT: Is there a tag to disable shadows in 24-bit?

http://dl.dropbox.com/u/5482530/a.out
http://tinyurl.com/y4g8ypw

You need both these files to run the example.
If you compile and run this code, you will get a grim reaper. The question is why.

Obviously it is IElf->RelocateSection() that is the problem. In the
autodocs it says:

"Note: If the section was absolute, or no reloc could be found for the
section, nothing happens and this function will return TRUE. The reason
for this is that really the intention was to have a usable, relocated section. It's not my fault if there was nothing to do..."

What I read from this is, that you can call RelocateSection() on any section without problems. This doesn't seem to be the case judging from the above code sample.


I'm trying to work on GDB, and this example has been distilled from Thomas Friedens sources in the adtools project. There seems to be a difference in the meaning of the Elf32_Shdr->sh_info member. In thomas' code it seems, that he expects it to contain the section number, but this makes GDB crash. The documentation on elf.library doesn't explain anything about the sctructures in <libraries/elf.h>, only the methods are described.

@ChrisH

Please read the previous posts again, I'm using flex here with Radeon 9250/128MB. Also, the problem is not the amount of video ram, because a comparatively high window doesn't display the same 'huckups' as a wide one.

@Elwood: If you try and run an autoscrolling screen in resolution 1280x1080 but with actual width set to 1920, you are able to reconstruct the same behavior in a smaller resolution.


Hmm, I guess people think that this is a pretty lame problem to bring up. Now consider this: I use Shell windows _all_ the time, and when opening a new shell with 'cli', you get a window, which covers the entire width of the wb screen. While I kind of like this "widescreen consol'ism", I hate the fact, that dragging the shell feels itchy, and I always end up resizing the shell to a little less than the entire width of the screen, just to get rid of this hick'ing. Is this lame? I don't know, you tell me

EDIT: Yeah I know, it's lame...

Just a note:

Has someone reported this problem (or maybe "problem")? I don't know
who to report to .


EDIT:

@MickJT:

But that doesn't make sense, since the shadow is both to the right and beneath the window, so a vertically extended window will also have a large shadow. My personal theory is, that it somehow has to do with the size of blocks or chunks that video memory can be allocated in, but then again, I don't know a thing about modern graphics chips design.