Page 1 of 1

Picture field

PostPosted: Sun Feb 16, 2014 4:21 pm
by mishem
If the extension does not match its image format.


Let me explain.

There is an image format *. Gif.
Changing this image format extension to *. Jpg.
Or vice versa.
(someone accidentally or specifically changed).

If we want to add a picture to the database, this will be a mistake.

Close this window is possible only through the Task Manager.

Such an error in the final application can lead to unpredictable consequences.

Re: Picture field

PostPosted: Mon Feb 17, 2014 2:34 am
by HPW

Loading images by their extension is the standard behaviour. Why should a file have a extension when not for that purpose.

When we would need to analyse the image-data before loading, this would raise the complexity and code-length much.

Of cource the load-error should be better catched and a more meanigfull real neobook-error should be generated.
This could be handled by neobook code.


Re: Picture field

PostPosted: Mon Feb 17, 2014 12:31 pm
by Neosoft Support
mishem are these things that show up during normal use of NeoBook or are you intentionally going out of your way to find new bugs?

Re: Picture field

PostPosted: Mon Feb 17, 2014 7:59 pm
by mishem
I knew that you would think so.


All this occurs during use.

I had such a file. I do not know where.
An error has occurred, I began to look for the cause.

At first he could not understand.

I thought that the reason for formatting fields.
Half a day searching for the error.
And accidentally realized that the case in the image.

I guess I'm just too much time to do NeoBook.

Re: Picture field

PostPosted: Tue Feb 18, 2014 12:14 pm
by Neosoft Support
OK, I will make sure this is added to the list of things to correct in the future. In the mean time, try to use the correct extensions on your image files.