Screengrab reacts better after lowering the font to 14.
Qpdfview now gives me the following message: unexpected tz val
Changing what you call native/non-native doesn't effect any Qt app I try as far as making it work better or worse. I thought disabling boopsi made some impact on screengrab but it was the smaller font.
* edit: now when I think about it the rendering of fonts regarding the Qpdfview distortion of fonts (kerning?) might be the answer - does it use a certain shared object library version? beacuse those have changed here and some I have put there myself (and softlinked) from various dev archives.
'Native' or BOOPSI menus only affect applications, that have menus. Obviously. The difference should be glaring.
I have only one version of the various shared objects. I have checked against the ones included with OS4.1 Final Edition, and have updated where necessary. What exactly are the shared objects, that you might have a different version of??
What I meant was regarding an affect on stuff that kinda lag or maybe are not working with an OS4 flow (the way a button "feels") so to speak or that have been reported here. Of course changing those settings have a visual and sometimes functional affect but I'm not always sure about better or worse. If it works well after all then I'll take it.
Well I updated for several files mosty about graphics and text (I'm pretty sure libpng has a positive affect on my system) - I added a pic of my shared object libs, as well as a dsi crashlog I'm getting from qcodeedit.
If you want to put Qt to the test maybe a port of the NEW Open Source Paint program that is getting a lot of excitement from artists on other platforms - Krita.
An update: after doing said experimentation with the prefs I now can't see anything amiga related with Juffed.
This sentence does not make any sense. I am completely unaware if this means, that the application does not start, if there is a problem loading 'amiga files' (whatever that would be) or if it is just a subjective statement, that the application 'does not look very amiga' any more.
Please be specific, when commenting on functional aspects of applications. So far, I have nothing that shows me how to solve your problem.
First: What did you do to make it try and open volume "Stuff" as a file??
Second: Did you change your filesystem, so the files "latestmonkey.txt" and "newfile.txt" should be unrecognizable?? I am thinking, renaming of volumes or folders, or moving the files somewhere else than they were originally created.
Third: The fontconfig error is also strange. Did you do as I suggested, namely try and erase the fontconfig cache files from sys:fonts/ ??
Probably i have found a way to lead SMTube to crash at startup, trying to launch two sessions simultanely ..
This is the error:
Quote:
terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc
Then it crash:
Quote:
Crash log for task "smtube" Generated by GrimReaper 53.19 Crash occured in module kernel at address 0x01810EA0 Type of crash: unknown exception Alert number: 0x81000009
[First: What did you do to make it try and open volume "Stuff" as a file??]
Well, nothing. File browser treats AmigaOS SFS+FFS Volumes as files after I played with the Qt settings (only ticking/unticking mixed with font changes which is now DejaVu Sans 14 and prefs returned to everything native). It also doesn't matter whether I open new text or old the behaviour stays the same.
[Second: Did you change your filesystem, so the files "latestmonkey.txt" and "newfile.txt" should be unrecognizable??]
Everything can be reproduced disregarding those conditions.
[Third: The fontconfig error is also strange. Did you do as I suggested, namely try and erase the fontconfig cache files from sys:fonts/ ??]
I did so after your second suggestion unfortunately it has no effect here.
Maybe next step should be deleting Juffed and opening a new one.
Well, unless I am able to reproduce the said conditions, I am probably not going to be able to fix them.
So a step by step guide on how you managed to get those outputs would be fitting. ;)
EDIT: The fontconfig error you are seeing is actually from fontconfig and has nothing to do with Qt. So there is a setup issue there on your system. Try deleting SYS:Fonts/fontconfig/fonts.conf and see, if that solves the issue.
Suddenly and with intent (or knowledge or any of that stuff...) I now have a theory!
I have mounted an Ext3 partition using a 3rd party driver. Juffed when clicked on the mounted partition opens instead (at last...) the mount command saved to a text file opened by mount which is loaded at start-up. The other drives it opens as empty text files/tabs - the same as if I pointed it to a specific text file (without using the built-in broswer).
Another behaviour is when I try to go back from the /qt/home it says "QFileSystemWatcher::addPath: path is empty".
But what will happen globally if I delete the font configuration file? Could the utility Eastern have something to do with it as it fails to convert the fonts to images and crashes (turned it off without effect on the issues).
Edited by Srtest on 2016/11/14 14:11:36 Edited by Srtest on 2016/11/14 14:14:34 Edited by Srtest on 2016/11/14 14:21:56 Edited by Srtest on 2016/11/14 14:23:47 Edited by Srtest on 2016/11/14 14:24:23
Guys... I deeply appologize. I have solved the puzzle... sort of...
It is a configuration issue, that gives problems with compatibility with certain apps built under a different configuration. For the moment, I have given up finding the way back to the starting point; it is simply too complicated.
I will puff out a fresh release of Qt with nothing added except for a fixed configuration. I will do a fair amount of testing beforehand, so it will take a little while. When that is done, I suggest, that all Qt apps - in use - are rebuilt against an updated set of includes and updated libraries. This is the only way of ensuring, that the problem goes away.
Sorry, I was a little too adventurous in the last release. Hope we can fix it this way.
@Srtest
Of course, this does not solve the issue with the fontconfig error. I am not sure, if this could be related to a custom file system. Perhaps. Also the text rendering flubber in qpdfview is probably not affected by this fix.
No need to apologize. Thank you for your work not only in listening to the users and being open about their way of doing stuff and their daily uses but also trying to accomplish a working stage considering different set-ups.
As for me if I'm able to add a percent to your 99 then I'm happy about it. Juffed became disfunctional after ticking/unticking the Qt options. Deleting + opening a new drawer fixed it and now it is working again so maybe that's another hint as far as the effect of changing Qt setting or maybe the Qt prefs app in itself or whatever - as long as it works.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
unfortunately it has no effect here.
