Bug#816447: marked as done (QImage ignore headers of jpg files)
Your message dated Tue, 1 Mar 2016 16:18:46 -0600
with message-id <20160301221846.GB6784@mira.lan.galacticasoftware.com>
and subject line Re: Bug#816447: QImage ignore headers of jpg files
has caused the Debian Bug report #816447,
regarding QImage ignore headers of jpg files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
816447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816447
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qtcreator
Version: 3.2.1
http://doc.qt.io/qt-4.8/qimage.html say "If the format is not
specified (which is the default), the loader probes the file for a
header to guess the file format.". Okay. I'm load any jpg file. Then,
rename this file into "test.png". After this I'm run simple test:
#include<QImage>
#include<cassert>
int main(int argc, char *argv[])
{
QImage test("test.png");
assert(!test.isNull());
return 0;
}
...SIGABRT. "Loader probes the file for a header"? Filename extension
is not a header. And yes, if jpg file have ".jpg" extension, I'm don't
get SIGABRT signal.
PS Same result in 3.6.0.
--- End Message ---
--- Begin Message ---
On Wed, Mar 02, 2016 at 12:54:46AM +0300, Strelok wrote:
> #include<QImage>
> #include<cassert>
>
> int main(int argc, char *argv[])
> {
> QImage test("test.png");
> assert(!test.isNull());
> return 0;
> }
This actually has nothing to do with QtCreator so closing.
Also, it works just fine with Qt5. I don't have Qt4 installed at the
moment to test, but most likely there is something else wrong. Most
likely, if you run from Qt Creator, currenct working directory is
*not* your source directory but the build directory. You can change
that in run settings, if you prefer. In other words, the file you are
looking for is not in place where the program is looking.
- Adam
--
Adam Majer
adamm@zombino.com
--- End Message ---
Reply to: