Wings Snapshot

[oort]

Not sure if this can be considered a bug since a person shouldn't do this... It happens in 1.4.1 as well.

Using Bend command Select Rod Center Vert.
Hit L
Crash

here is the dump

Dump written 2012-12-21_16-26
Version: 1.5.pre1.38.g62be8
Window: geom
Reason: function_clause

Short stack trace:
[]

Long stack trace:
[{e3d_bv,box,[[]],[{file,"e3d_bv.erl"},{line,54}]},
{e3d_vec,bounding_box,1,[{file,"e3d_vec.erl"},{line,292}]},
{wings_sel,fold_1,4,[{file,"wings_sel.erl"},{line,84}]},
{wings_vec,check_point,1,[{file,"wings_vec.erl"},{line,735}]},
{wings_vec,handle_event_4,3,[{file,"wings_vec.erl"},{line,196}]},
{wings_wm,handle_event,3,[{file,"wings_wm.erl"},{line,824}]},
{wings_wm,send_event,2,[{file,"wings_wm.erl"},{line,796}]},
{wings_wm,do_dispatch,2,[{file,"wings_wm.erl"},{line,698}]}]

[Fonte Boa]

Bingo, oort!
I can confirm this here too, developers!
(congratulations, oortman)

It is a severous one, imo, since i can reproduce it during other Secondary Selection operations!!!
For example, during an Scale Axis operation, using standard Magnet, when i pick a vert to define outer boundary, and hit L, wings crashes too:

Dump written 2012-12-21_19-33
Version: 1.4
Window: geom
Reason: function_clause

Short stack trace:
[{e3d_bv,box,1},
{e3d_vec,bounding_box,1},
{wings_sel,fold_1,4},
{wings_vec,check_magnet_point,1},
{wings_vec,handle_event_4,3},
{wings_wm,handle_event,3},
{wings_wm,send_event,2},
{wings_wm,do_dispatch,2}]

Long stack trace:
[{e3d_bv,box,[[]]},
{e3d_vec,bounding_box,1},
{wings_sel,fold_1,4},
{wings_vec,check_magnet_point,1},
{wings_vec,handle_event_4,3},
{wings_wm,handle_event,3},
{wings_wm,send_event,2},
{wings_wm,do_dispatch,2}]

After this, if i try use the same command (Scale Axis), wings crashes again and force the restart:

Dump written 2012-12-21_19-37
Version: 1.4
Window: geom
Reason: function_clause

Short stack trace:
[{wings_vec,'-handle_event/3-fun-0-',3},
{wings_dl,map_1,5},
{wings_vec,handle_event,3},
{wings_wm,handle_event,3},
{wings_wm,send_event,2},
{wings_wm,do_dispatch,2},
{wings_wm,get_and_dispatch,0},
{wings,init,1}]

Long stack trace:
[{wings_vec,'-handle_event/3-fun-0-',
[{dlo,1,none,5,3,none,4,2,none,
{vab,
{24,
<<0,0,128,191,0,0,128,191,0,0,128

etc etc

EDIT
Same crash dump after a mmb Flatten!!!!!!!!!!!!!!!!!!! (when i select the Flatten point and hit L)

EDIT2
I tried all the keyboard keys: the problem is just with "L"

[micheus]

EDIT

Sorry, there isnt really a bug about this in last snapshot. The reason of that problem, Micheus, is the wings_tweak.beam file you distributed to be tested at http://www.wings3d.com/forum/showthread....815#pid815
Can you give a look there to know what is going on?

Of course I can. I think it's already fixed - that I didn't make it available for download, sorry. I'll do this tomorow. (I'm on the phone now )

[micheus]

Fixed.
https://github.com/Micheus/wings/commit/...78d6d567d6

Fonte, sorry for not have tested it in the Quick Smooth Preview mode.

I have an new folder on my Google drive to upload the beams for this snapshot: 1.5-pre1 (please, download the files and try it).

Thanks

[micheus]

Using Bend command Select Rod Center Vert.
Hit L
Crash

For example, during an Scale Axis operation, using standard Magnet, when i pick a vert to define outer boundary, and hit L, wings crashes too:
EDIT
Same crash dump after a mmb Flatten!!!!!!!!!!!!!!!!!!! (when i select the Flatten point and hit L)
EDIT2
I tried all the keyboard keys: the problem is just with "L"

I tried, but I couldn't repeat the crash. When I hit "L" key the sel mode just change to edge and some edge loop is selected. (I used the official snapshot)

[Fonte Boa]

Be sure you are in Vertex Mode at the moment you hit "L" key
(during any secondary selection step of a command, like Clamped Bend)

[optigon]

Be sure you are in Vertex Mode at the moment you hit "L" key
(during any secondary selection step of a command, like Clamped Bend)

I'll fix this one. Thanks for the report guys!

[optigon]

Be sure you are in Vertex Mode at the moment you hit "L" key
(during any secondary selection step of a command, like Clamped Bend)

Fixed.
https://github.com/optigon/wings/commit/...dc254b1acd

[oort]

I miss having the cube primitive default with number of cuts set to a value of 1. I guess the ideal for me would be for wings3D to remember the previous setting.

oort

[maker]

I'm confused. R-click|Cube. Don't you get the "old" default cube? (Clicking on box gives the new, sexy one with the macho cuts )