QT SDK feedback and questions

@kas1e

Thanks, I'm on it now!

Also expect a shiny new upload in just a minute.

(After all, it was not as bad as I thought when I checked into amigans last night and saw all the bug reports. I think most is fixed now, phew )

@alkfil
Quote:
As all the time. Good programmer hold the first feels, and found a solutions later, bad programmers found any excuses to not find the solutions and only talk about how hard to implent that or that. If only 10 programmers like you for os4, its for few years will growup a lot !

@kas1e

Check your email!

@alfkil
Check now yours plz :)

@alfkil is the alignment of the fonts fixed as well in the new sdk?

Alignment of fonts should be ok now. Also if you try the texteditor demo, you will see, that bold and italic styles work now.

One thing that I have not solved is the size difference btw freetype and native fonts. I think this is due to a conceptual difference: One counts the _font height_, the other one the _font size_:

http://www.emdpi.com/fontsize.html

I currently have no idea how to solve this.

it's not a point vs pixel thing?

@spotUP

No, I have checked, and both point and pixel sizes are the same. And dpi is set to 72, so they should be.

Quote:I'd say: Don't.

If I'm not mistaken, this is happening in most or all existing Amiga WPs and other programs rendering fonts. If you switch between the font types, you often have to adjust the size. IMHO, solving (or rather, working around) that is not worth much work, at least.

Best regards,

Niels

Niels, what do you suggest? That it shouldn't get fixed???

Yes, at least not if it turns out to require much work. I'd rather Alfkil spent that effort on more pressing fixes and enhancements.

Just my 2 øre, of course.

Best regards,

Niels

Well the font issues are fixed now anyway, thanks a lot Alfkil. I just released my first tiny porting test app called ipqalc. enjoy! =) more to come!

@alkfil
Don't forget plz about my 2 reports as well (the missing of every second mouse button pressing and wrong chords in the apps where you use pencil for drawing).

Its happens in FlasQ and in EasyPaint as well (i.e. something common)

qmake fails with tiled:
http://qt-apps.org/content/show.php/Tiled?content=128860

6.Bob:Coding/Projects/qt/tiled-qt-0.6.0> qmake
Project ERROR: QT_VERSION not defined. Tiled does not work with Qt 3.

@kas1e

I haven't forgotten: The "two click" issue should be fixed in the latest version, no? If not, please report it again and tell me how to reproduce.

The "wrong coords" issue is just laziness from my side, should be trivial to fix .

@alkfil
I install firstly latest QT-User from os4depot (via update in installer script) : flasq and easypaint still have same problems.

Then i install latest qt-sdk from os4depot (via update in installer script as well), and recompile easypaint from scratch: sadly to say all the bugs still here, i.e:

1. "open" do nothing
2. missing next mouse pressing still (just try to run easypaint, make a new tab, so you will have 2, and try to swith beetwen them)
3. mouse chords for the pencil still wrong.

That all when everything "native" enabled.

ps. check mail as well

I have a problem when i try to port qt-apps. I get the same error as the thread below. Is there any easy solution for this?
http://forum.hyperion-entertainment.biz/viewtopic.php?f=27&t=772

@Joeled

I'm confused: Do you have a problem with the SDK or with Qt? The thread you refered to talks about makelink failing during installation of the SDK, if that is your problem, then that is a subject of another thread. If you have a Qt specific problem, then please state it so I can examine it.

@alfkil
Sorry wrong place. Maybe someone can move it?

@Joeled:

Why don't you just tell me what the problem is?