[fixed] Snap Image window suddenly close by particular image data.

[tkbd]

On snap image command,some image data caused that error log created or snap image window was close suddenly.
It caused when select an image by pulldown menu in snap image window.
(Note:The state is non-active display)

Test image files are here.
http://brace.client.jp/wings3d_141/img_prj/test_images.zip

I checked it both of Wings3D v2.2.5 and v2.2.4, and it caused on Wings3D v2.2.5 only .

For example

Quote:At first: these file are Ok
tree_dds_dxt5_GC9.dds --- OK
tree_gifcutout.gif ---- OK
tree_jpg.jpg -------OK

Next, When Add a particular image data(tga24_PSElement9.tdg etc) by imported.
I descovered that If select an image more bellow than the problem image data in the menu list, the snap image window will close.

tree_dds_dxt5_GC9.dds --Ok
tree_gifcutout.gif --- OK
tree_tga24_PSElement9.tga ---- the window suddenly close
tree_jpg.jpg ---- the window suddenly close ( !? )


The image files that caused the problem.
tree_bmp32_alpha_preview.bmp -- Output Error log
tree_bmp16.bmp --- Snap image window close suddenly
tree_bmp24.bmp
tree_bmp32_alpha_pixelmator3.bmp
tree_tga24_PSElement9.tga

Error log is here
(Note:It is display that dot-extension with filename, but the data were imported as Internal Image )

Code:

Dump written 2020-5-13_16-47
Version: 2.2.5
Window: [wpc_snap_win,<0.255.0>]
Reason: {badmatch,{e3d_image,r8g8b8,3,1,lower_left,256,256,
                             <<"FF FF FF FF FF FF FF"...>>,
                             "//Users/user/Desktop/test_images/tree_bmp32_no_alpha.bmp",
                             "tree_bmp32_no_alpha.bmp",[]}}

Stack trace:
[{wpc_snap_win,handle_event,2,[{file,"wpc_snap_win.erl"},{line,664}]},
{wx_object,handle_msg,5,[{file,"wx_object.erl"},{line,468}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]

Code:

Dump written 2020-5-13_16-54
Version: 2.2.5
Window: [wpc_snap_win,<0.210.0>]
Reason: {badmatch,{e3d_image,r8g8b8a8,4,1,lower_left,256,256,
                             <<255,255,255,0,255,255,255,0,255,...>>,
                             "//Users/user/Desktop/test_images/tree_dds_dxt5_GC9.dds",
                             "tree_dds_dxt5_GC9.dds2",[]}}

Stack trace:
[{wpc_snap_win,handle_event,2,[{file,"wpc_snap_win.erl"},{line,664}]},
{wx_object,handle_msg,5,[{file,"wx_object.erl"},{line,468}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]

-------
tkbd

[micheus]

tkbd, I'm getting an 403 error when trying to download the zip file.

[tkbd]

I have forgot that server doesn't allow external-access for direct link for a file.
To download the file to access a following URL.
http://brace.client.jp/wings3d_141/file.html

Look for the following phrase in the middle of the page:
There is a download link.

Quote:Image Test Files
Which a texture format can/can't import to Wings3D? To be prepared in various types of files is very hard.
So,These files can use for test,Wings3D Tryout,Plugin Development,Debugging,and BUG report etc

[tkbd]

I test it with Snap Image tool on v2.2.6.
Then I got same error result.

I use these images and tried them in the AutoUV image mixer menu.
AutoUV Shader plugin
No error happend.
So,This may happen only with the Image Snap Tool.

If it has a difference....
The Image Snap tool used a special type of pull-down menu.
It has a text input field(It is for search in list?).

[tkbd]

Is this bug related to this SnapImage window error?
I'll put up a link for reference.
Snap Image window error(Wings3D forum)

[dgud]

Same bug, but there must be something strange with the file names, they look the same
but are different when returned from the pulldown menu.

Fixed by no longer crashing when they are not exactly the same.

[tkbd]

dgud,Thank you for many error countermeasures.

Afterward ,I also tested a lot of cases by changed on imported image file content, size, name ,formats etc.
Finally,I have identified the simple conditions under which this issue occurs.

I thought that may be due to the file order, not the file name.
I upload an image, the error reproducible steps and comparisons are illustrated below the image.