<![CDATA[Wings 3D Development Forum - Programming]]> https://www.wings3d.com/forum/ Thu, 07 May 2026 15:33:00 +0000 MyBB <![CDATA["How to" about context menus]]> https://www.wings3d.com/forum/showthread.php?tid=3116 Wed, 24 May 2023 15:00:05 +0000 micheus]]> https://www.wings3d.com/forum/showthread.php?tid=3116 It's not finished yet, so I going to keep adding any other information I remember here.

I hope this can at least help other to get a start point to find their own understanding. Smile


I'm going to start by spotting that in order to support multiple languages (translations) we must to use the macro ?__(<index>, <label>) in every place a text needs to be translated. This means menus, dialogs, windows, etc. The index must be unique for functions with the same name, which means we can reuse them in any other function in the same module without any problem.

All module/plugin that implements menus/sub-menus must export a menu/2 function;
Code:
export([menu/2, ...])


The function get two parameters which the first is the parent's Id and the second a list having its options (the menu itself);
Code:
menu({<id>}, <options_list>)

So, to append an menu option to the main menu as the Tools we can check for that this way:
PHP Code:
menu({tolls}, Menu) ->
    MyMenu = build_my_menu(),
    Menu ++ MyMenu;
menu(_, Menu) ->
    Menu.

build_my_menu() ->
    [{?__(1, "My Option"), my_option, ?__(2, "My single option for LMB")}]. 


In Wings3D, a menu option can have three different responses depending on which mouse button was used to select it. We refer them as LMB, MMB and RMB action (Left, Middle and Right mouse button, respectively).

A simple option, which the action is activated by pressing LMB, is constructed by using a tuple with three elements:
Code:
{<label>, <id>, <description/hint>}

It will look like this (option and description/hint/tooltip):
[Image: w3d-menu-single.png]

If the the action will have the option to show the user a input dialog instead of only to run the action directly, then the item must includes a 4th parameter to indicate that which will result in a small gerar icon be shown in the right corner of the option when the menu is shown:
Code:
{<label>, <id>, <description/hint>, [option]}

in this case our menu item would look like this:
PHP Code:
build_my_menu() ->
    [{?__(1, "My Option"), my_option, ?__(2, "My single option for LMB")}, [option]]. 

It will look like this (the [option] parameter will automatically add a second command/hint for RMB):
[Image: w3d-menu-single-option.png]


Multiple options, which the action is activated by others buttons than only pressing LMB, is constructed by using a list of tuples similar to the single option one, but the id will be get from a pick option function which will handle the button clicked and now the 3rd parameter is a tuple that contains the description for each button option. If an mouse option will not be used its respective description must be an empty list ([]). The 4th parameter stays optional and will keep working for LMB option only:
Code:
{<label>, <click_function>, {<description/hint LMB>, <description/hint MMB>, <description/hint RMB>}}

This click_function is a function that will return the real function that handle the mouse buttons pressed (or help atom). The mouse_button value is 1, 2 and 3 for LMB, MMB and RMB respectively:

Code:
<click_function>() ->
    fun
        (<help|mouse_button>, _Ns) -> <command>;
        (_, _) -> ignore
    end.
* that _Ns parameter I don't know exactly what it stands for, but it is used in directions function we can find in wings_util.erl and is used to assembly commands and help information for menus.

in this case our menu item would be defined like this:
PHP Code:
build_my_menu() ->
    [{?__(1, "My Option"), my_menu_items(), {?__(2, "My option 1 for LMB"),
                                            ?__(3, "My option 2 for MMB"),
                                            ?__(4, "My option 3 for RMB")} }].

my_menu_items() ->
    fun
        (1, _) -> {my_option, opt1};
        (2, _) -> {my_option, opt2};
        (3, _) -> {my_option, opt3};
        (_, _) -> ignore
    end. 

and it will look like this:
[Image: w3d-menu-multiple-3.png]

if we define only options for LMB and RMB, for instance, it can look like this:
[Image: w3d-menu-multiple-2.png]


"Pure" sub-menus are constructed in a similar way as menu items, but it doesn't need a description (because it's not used) and we use a set <id,function> to create the menu cascade. This function will return a list of menu items. In case on of these items have a sub-menu we repeat this structure all over:
Code:
{<label>, <{id, build_submenu_fun}>}

build_submenu_fun() ->
    [{<label>, <id>, <description/hint>, [option]},
     :
     {<label>, <id>, <description/hint>, [option]}]

and then it can have this look:
PHP Code:
build_my_menu() ->
    [{?__(1,"My menu"), {my_menu, build_submenu()}}]

build_submenu() ->
    [{?__(1, "My option 1 for submenu level 1"), id_option1, ?__(2, "Description of my option 1")},
     {?__(3, "My option 2 for submenu level 1"), my_menu_items() , {?__(4, "Description of my option 2 LMB"),
                                                                   [],
                                                                   ?__(5, "Description of my option 2 RMB")}].

my_menu_items() ->
    fun
        (1, _) -> {my_option, opt1};
        (3, _) -> {my_option, opt2};
        (_, _) -> ignore
    end. 

Here is how a "pure" sub-menu item will look like:
[Image: w3d-menu-submenu.png]

and in this one there are three actions for the item which the action for LMB will call a sub-menu (lets call it mixed menu/sub-menus):
[Image: w3d-menu-multiple-submenu.png]


Menus can also have check marked options. We create them by providing as 4th parameter with a list with a single tuple this way:
Code:
{<label>, <id>, <description/hint>, [{crossmark, <boolean_value>}]}

in this case our menu item would look like this:
PHP Code:
build_my_menu() ->
    [{?__(1, "My Option"), my_check_option, ?__(2, "My single option for LMB"), 
                      [{crossmark, wings_pref:get_value(my_check_pref, false)}]]. 
In this case we are checking for the my_check_pref id stored in the preferences and giving it a default value false.

The result is something like this:
[Image: menus-checkmark.png]

Default preferences values can be defined in a module using the init/0 function.



p.s.: The elements not delimited by '<' and '>' are kept as they are in the code.]]> It's not finished yet, so I going to keep adding any other information I remember here.

I hope this can at least help other to get a start point to find their own understanding. Smile


I'm going to start by spotting that in order to support multiple languages (translations) we must to use the macro ?__(<index>, <label>) in every place a text needs to be translated. This means menus, dialogs, windows, etc. The index must be unique for functions with the same name, which means we can reuse them in any other function in the same module without any problem.

All module/plugin that implements menus/sub-menus must export a menu/2 function;
Code:
export([menu/2, ...])


The function get two parameters which the first is the parent's Id and the second a list having its options (the menu itself);
Code:
menu({<id>}, <options_list>)

So, to append an menu option to the main menu as the Tools we can check for that this way:
PHP Code:
menu({tolls}, Menu) ->
    MyMenu = build_my_menu(),
    Menu ++ MyMenu;
menu(_, Menu) ->
    Menu.

build_my_menu() ->
    [{?__(1, "My Option"), my_option, ?__(2, "My single option for LMB")}]. 


In Wings3D, a menu option can have three different responses depending on which mouse button was used to select it. We refer them as LMB, MMB and RMB action (Left, Middle and Right mouse button, respectively).

A simple option, which the action is activated by pressing LMB, is constructed by using a tuple with three elements:
Code:
{<label>, <id>, <description/hint>}

It will look like this (option and description/hint/tooltip):
[Image: w3d-menu-single.png]

If the the action will have the option to show the user a input dialog instead of only to run the action directly, then the item must includes a 4th parameter to indicate that which will result in a small gerar icon be shown in the right corner of the option when the menu is shown:
Code:
{<label>, <id>, <description/hint>, [option]}

in this case our menu item would look like this:
PHP Code:
build_my_menu() ->
    [{?__(1, "My Option"), my_option, ?__(2, "My single option for LMB")}, [option]]. 

It will look like this (the [option] parameter will automatically add a second command/hint for RMB):
[Image: w3d-menu-single-option.png]


Multiple options, which the action is activated by others buttons than only pressing LMB, is constructed by using a list of tuples similar to the single option one, but the id will be get from a pick option function which will handle the button clicked and now the 3rd parameter is a tuple that contains the description for each button option. If an mouse option will not be used its respective description must be an empty list ([]). The 4th parameter stays optional and will keep working for LMB option only:
Code:
{<label>, <click_function>, {<description/hint LMB>, <description/hint MMB>, <description/hint RMB>}}

This click_function is a function that will return the real function that handle the mouse buttons pressed (or help atom). The mouse_button value is 1, 2 and 3 for LMB, MMB and RMB respectively:

Code:
<click_function>() ->
    fun
        (<help|mouse_button>, _Ns) -> <command>;
        (_, _) -> ignore
    end.
* that _Ns parameter I don't know exactly what it stands for, but it is used in directions function we can find in wings_util.erl and is used to assembly commands and help information for menus.

in this case our menu item would be defined like this:
PHP Code:
build_my_menu() ->
    [{?__(1, "My Option"), my_menu_items(), {?__(2, "My option 1 for LMB"),
                                            ?__(3, "My option 2 for MMB"),
                                            ?__(4, "My option 3 for RMB")} }].

my_menu_items() ->
    fun
        (1, _) -> {my_option, opt1};
        (2, _) -> {my_option, opt2};
        (3, _) -> {my_option, opt3};
        (_, _) -> ignore
    end. 

and it will look like this:
[Image: w3d-menu-multiple-3.png]

if we define only options for LMB and RMB, for instance, it can look like this:
[Image: w3d-menu-multiple-2.png]


"Pure" sub-menus are constructed in a similar way as menu items, but it doesn't need a description (because it's not used) and we use a set <id,function> to create the menu cascade. This function will return a list of menu items. In case on of these items have a sub-menu we repeat this structure all over:
Code:
{<label>, <{id, build_submenu_fun}>}

build_submenu_fun() ->
    [{<label>, <id>, <description/hint>, [option]},
     :
     {<label>, <id>, <description/hint>, [option]}]

and then it can have this look:
PHP Code:
build_my_menu() ->
    [{?__(1,"My menu"), {my_menu, build_submenu()}}]

build_submenu() ->
    [{?__(1, "My option 1 for submenu level 1"), id_option1, ?__(2, "Description of my option 1")},
     {?__(3, "My option 2 for submenu level 1"), my_menu_items() , {?__(4, "Description of my option 2 LMB"),
                                                                   [],
                                                                   ?__(5, "Description of my option 2 RMB")}].

my_menu_items() ->
    fun
        (1, _) -> {my_option, opt1};
        (3, _) -> {my_option, opt2};
        (_, _) -> ignore
    end. 

Here is how a "pure" sub-menu item will look like:
[Image: w3d-menu-submenu.png]

and in this one there are three actions for the item which the action for LMB will call a sub-menu (lets call it mixed menu/sub-menus):
[Image: w3d-menu-multiple-submenu.png]


Menus can also have check marked options. We create them by providing as 4th parameter with a list with a single tuple this way:
Code:
{<label>, <id>, <description/hint>, [{crossmark, <boolean_value>}]}

in this case our menu item would look like this:
PHP Code:
build_my_menu() ->
    [{?__(1, "My Option"), my_check_option, ?__(2, "My single option for LMB"), 
                      [{crossmark, wings_pref:get_value(my_check_pref, false)}]]. 
In this case we are checking for the my_check_pref id stored in the preferences and giving it a default value false.

The result is something like this:
[Image: menus-checkmark.png]

Default preferences values can be defined in a module using the init/0 function.



p.s.: The elements not delimited by '<' and '>' are kept as they are in the code.]]> <![CDATA[Export to a temp .obj and import from temp .obj]]> https://www.wings3d.com/forum/showthread.php?tid=2978 Sun, 17 Jan 2021 04:07:13 +0000 morikan]]> https://www.wings3d.com/forum/showthread.php?tid=2978
I do not know anything about Erlang. I am wondering how hard it would be to implement a simple plugin that would let me implement exporting to a temp.obj and importing from temp.obj

I want this so that I can exchange files between other apps and Wings quickly.

thanks]]>
I do not know anything about Erlang. I am wondering how hard it would be to implement a simple plugin that would let me implement exporting to a temp.obj and importing from temp.obj

I want this so that I can exchange files between other apps and Wings quickly.

thanks]]> <![CDATA[New UV Mapping Option]]> https://www.wings3d.com/forum/showthread.php?tid=2901 Sun, 26 Jan 2020 20:48:28 +0000 some_yahoo]]> https://www.wings3d.com/forum/showthread.php?tid=2901
Wings wants to unwrap it all in a pinwheel. What I'd like is a way to perform the following "macro"

  1. Find the longest side of the polygon (object level of course, not face)
  2. Rotate until that side is horizontal.
  3. Do this on as many items as are selected.

After that, I can align them all center, do a 180 flip on any that are upside down, and scale to taste.

Is there anything like that, or alternately how do I get started writing a plugin for this beast?

Because I have hundreds of these to rotate and align, and a computer would be able to do this in a flash.

.jpg   Capture.JPG (Size: 115.83 KB / Downloads: 10) ]]>
Wings wants to unwrap it all in a pinwheel. What I'd like is a way to perform the following "macro"

  1. Find the longest side of the polygon (object level of course, not face)
  2. Rotate until that side is horizontal.
  3. Do this on as many items as are selected.

After that, I can align them all center, do a 180 flip on any that are upside down, and scale to taste.

Is there anything like that, or alternately how do I get started writing a plugin for this beast?

Because I have hundreds of these to rotate and align, and a computer would be able to do this in a flash.

.jpg   Capture.JPG (Size: 115.83 KB / Downloads: 10) ]]> <![CDATA[[fixed]can't find the cl.exe]]> https://www.wings3d.com/forum/showthread.php?tid=2882 Fri, 03 Jan 2020 08:25:42 +0000 nigec]]> https://www.wings3d.com/forum/showthread.php?tid=2882 The path for cl.exe is set for vs2017 but I'm guessing something is wrong for my msys64 setup?

the header files for OpenCL and the lib are there from the nvidia sdk
C:\wingsdev\msys64\usr\include\opencl.h (and the other files in the sdk folder)
C:\wingsdev\msys64\usr\lib\OpenCL.lib

I don't "need" it working but I guess it would be nice if it did lol

I'm currently looking at my Thea script but I'm considering porting it for Luxcore.. which is probably the best free option these days
if Wings had a ply exporter that would be really easy!!

edit..
after some messing about I now get:
Code:
$ rebar compile
==> cl (compile)
make: Entering directory '/c/wingsdev/src/cl/c_src'
make nif TYPE=release
make[1]: Entering directory '/c/wingsdev/src/cl/c_src'
gcc -c -ocl_nif.o -Wall -Wextra -Wswitch-default -Wswitch-enum -D_THREAD_SAFE -D_REENTRANT -fno-common -Wno-deprecated-declarations -Wno-missing-field-initializers -I"c:/Program Files/erl10.5/usr/include" cl_nif.c
/bin/sh: gcc: command not found
make[1]: *** [Makefile:188: cl_nif.o] Error 127
make[1]: Leaving directory '/c/wingsdev/src/cl/c_src'
make: *** [Makefile:167: all] Error 2
make: Leaving directory '/c/wingsdev/src/cl/c_src'
ERROR: Command [compile] failed!


edit2:
you can get the include and lib files here:
https://github.com/GPUOpen-LibrariesAndS...K/releases]]> The path for cl.exe is set for vs2017 but I'm guessing something is wrong for my msys64 setup?

the header files for OpenCL and the lib are there from the nvidia sdk
C:\wingsdev\msys64\usr\include\opencl.h (and the other files in the sdk folder)
C:\wingsdev\msys64\usr\lib\OpenCL.lib

I don't "need" it working but I guess it would be nice if it did lol

I'm currently looking at my Thea script but I'm considering porting it for Luxcore.. which is probably the best free option these days
if Wings had a ply exporter that would be really easy!!

edit..
after some messing about I now get:
Code:
$ rebar compile
==> cl (compile)
make: Entering directory '/c/wingsdev/src/cl/c_src'
make nif TYPE=release
make[1]: Entering directory '/c/wingsdev/src/cl/c_src'
gcc -c -ocl_nif.o -Wall -Wextra -Wswitch-default -Wswitch-enum -D_THREAD_SAFE -D_REENTRANT -fno-common -Wno-deprecated-declarations -Wno-missing-field-initializers -I"c:/Program Files/erl10.5/usr/include" cl_nif.c
/bin/sh: gcc: command not found
make[1]: *** [Makefile:188: cl_nif.o] Error 127
make[1]: Leaving directory '/c/wingsdev/src/cl/c_src'
make: *** [Makefile:167: all] Error 2
make: Leaving directory '/c/wingsdev/src/cl/c_src'
ERROR: Command [compile] failed!


edit2:
you can get the include and lib files here:
https://github.com/GPUOpen-LibrariesAndS...K/releases]]> <![CDATA[32bit Linux]]> https://www.wings3d.com/forum/showthread.php?tid=2878 Thu, 02 Jan 2020 08:12:38 +0000 nigec]]> https://www.wings3d.com/forum/showthread.php?tid=2878 Raspbian is installed on a laptop not a Pi, I had considered trying to build Wings but the tut is out of date and I get the feeling I'm setting myself up to fail, I'm not Linux savvy so if it goes wrong I doubt I could solve it..
Is there a recent 32bit version?

I have Raspbian because its faster than Lubuntu but sadly the desktop environment is 32bit]]> Raspbian is installed on a laptop not a Pi, I had considered trying to build Wings but the tut is out of date and I get the feeling I'm setting myself up to fail, I'm not Linux savvy so if it goes wrong I doubt I could solve it..
Is there a recent 32bit version?

I have Raspbian because its faster than Lubuntu but sadly the desktop environment is 32bit]]> <![CDATA[how to make plugins from the command line]]> https://www.wings3d.com/forum/showthread.php?tid=2681 Sat, 08 Sep 2018 22:00:27 +0000 hartsantler]]> https://www.wings3d.com/forum/showthread.php?tid=2681
Code:
BuildShape = fun(Prefix, Fs, Vs, PostFix) ->
    We = wings_we:build(Fs, Vs),
    Name = Prefix++PostFix,
    St = wpa:get_state(),
    Shapes0 = element(1, St),
    Shapes = gb_trees:insert(0, We, Shapes0),
    erlang:setelement(1, St, Shapes) end.

Tetrahedron = fun(L, PostFix) ->
    Xi = L/2.0,
    Hp = math:sqrt(3.0),
    Li = Xi*Hp,
    Zi = Xi/Hp,
    Yi = L * math:sqrt(2.0/3.0),
    Yf = Yi / 3.0,

    Fs = [[2,1,0],[1,2,3],[1,3,0],[3,2,0]],
    Vs0 = [{ 0.0,  Yi-Yf,  0.0},
       { 0.0, -Yf,   Li-Zi},
       { -Xi, -Yf,     -Zi},
       {  Xi, -Yf,     -Zi}],
    BuildShape("tetrahedron", Fs, Vs0, PostFix) end.

Tetrahedron(1.0, "1").

The error i get is:
Code:
** exception error: no function clause matching
                    gb_trees:insert(0,
                                    {we,undefined,0,[],
                                     {array,6,10,undefined,
                                      {{edge,0,1,2,0,4,2,1,3},
                                       {edge,0,2,0,3,3,0,2,5},
                                       {edge,0,3,3,2,5,1,0,4},
                                       {edge,1,2,1,0,5,4,0,1},
                                       {edge,1,3,2,1,2,0,3,5},
                                       {edge,2,3,1,3,4,3,1,2},
                                       undefined,undefined,undefined,
                                       undefined}},
                                     none,none,
                                     {4,
                                      {2,0,
                                       {1,3,{0,0,nil,nil},nil},
                                       {3,1,nil,nil}}},
                                     {0,nil},
                                     {array,4,10,undefined,
                                      {0,0,1,2,undefined,undefined,undefined,
                                       undefined,undefined,undefined}},
                                     {array,4,10,undefined,
                                      {{0.0,0.5443310539518174,0.0},
                                       {0.0,-0.2721655269759087,
                                        0.5773502691896257},
                                       {-0.5,-0.2721655269759087,
                                        -0.2886751345948129},
                                       {0.5,-0.2721655269759087,
                                        -0.2886751345948129},
                                       undefined,undefined,undefined,
                                       undefined,undefined,undefined}},
                                     {0,nil},
                                     default,6,none,none,[]},
                                    st) (gb_trees.erl, line 276)
]]>
Code:
BuildShape = fun(Prefix, Fs, Vs, PostFix) ->
    We = wings_we:build(Fs, Vs),
    Name = Prefix++PostFix,
    St = wpa:get_state(),
    Shapes0 = element(1, St),
    Shapes = gb_trees:insert(0, We, Shapes0),
    erlang:setelement(1, St, Shapes) end.

Tetrahedron = fun(L, PostFix) ->
    Xi = L/2.0,
    Hp = math:sqrt(3.0),
    Li = Xi*Hp,
    Zi = Xi/Hp,
    Yi = L * math:sqrt(2.0/3.0),
    Yf = Yi / 3.0,

    Fs = [[2,1,0],[1,2,3],[1,3,0],[3,2,0]],
    Vs0 = [{ 0.0,  Yi-Yf,  0.0},
       { 0.0, -Yf,   Li-Zi},
       { -Xi, -Yf,     -Zi},
       {  Xi, -Yf,     -Zi}],
    BuildShape("tetrahedron", Fs, Vs0, PostFix) end.

Tetrahedron(1.0, "1").

The error i get is:
Code:
** exception error: no function clause matching
                    gb_trees:insert(0,
                                    {we,undefined,0,[],
                                     {array,6,10,undefined,
                                      {{edge,0,1,2,0,4,2,1,3},
                                       {edge,0,2,0,3,3,0,2,5},
                                       {edge,0,3,3,2,5,1,0,4},
                                       {edge,1,2,1,0,5,4,0,1},
                                       {edge,1,3,2,1,2,0,3,5},
                                       {edge,2,3,1,3,4,3,1,2},
                                       undefined,undefined,undefined,
                                       undefined}},
                                     none,none,
                                     {4,
                                      {2,0,
                                       {1,3,{0,0,nil,nil},nil},
                                       {3,1,nil,nil}}},
                                     {0,nil},
                                     {array,4,10,undefined,
                                      {0,0,1,2,undefined,undefined,undefined,
                                       undefined,undefined,undefined}},
                                     {array,4,10,undefined,
                                      {{0.0,0.5443310539518174,0.0},
                                       {0.0,-0.2721655269759087,
                                        0.5773502691896257},
                                       {-0.5,-0.2721655269759087,
                                        -0.2886751345948129},
                                       {0.5,-0.2721655269759087,
                                        -0.2886751345948129},
                                       undefined,undefined,undefined,
                                       undefined,undefined,undefined}},
                                     {0,nil},
                                     default,6,none,none,[]},
                                    st) (gb_trees.erl, line 276)
]]> <![CDATA[batch importer]]> https://www.wings3d.com/forum/showthread.php?tid=2680 Sat, 08 Sep 2018 16:12:34 +0000 hartsantler]]> https://www.wings3d.com/forum/showthread.php?tid=2680 I'm new to erlang, and taken a look at the code in: e3d_obj.erl, wings_console.erl, wings_start.erl, wpa.erl, wpc_collada.erl, and wings_plugin.erl.

So far i have this code, which loads my obj, but then fails to update the view or show it in the Wings UI. What am i missing?

Code:
{ok, E3DFile} = e3d_obj:import("/home/username/test.obj").
St0 = wpa:get_state().
wings_import:import(E3DFile, St0).

https://github.com/dgud/wings/issues/298]]> I'm new to erlang, and taken a look at the code in: e3d_obj.erl, wings_console.erl, wings_start.erl, wpa.erl, wpc_collada.erl, and wings_plugin.erl.

So far i have this code, which loads my obj, but then fails to update the view or show it in the Wings UI. What am i missing?

Code:
{ok, E3DFile} = e3d_obj:import("/home/username/test.obj").
St0 = wpa:get_state().
wings_import:import(E3DFile, St0).

https://github.com/dgud/wings/issues/298]]> <![CDATA[About the windows hierarchy]]> https://www.wings3d.com/forum/showthread.php?tid=2671 Mon, 30 Jul 2018 15:33:47 +0000 micheus]]> https://www.wings3d.com/forum/showthread.php?tid=2671 wxWidgets library as the new UI (user interface). Maybe it can be useful to any (future) new coders too.
Not all controls/events/functions - available in the wxWidgets library - are exposed to us by Erlang. To know what is available we can check the help page for wx module.

In this layout we can see the way the windows are stored in the preferences file as well as how they are constructed in the memory. The windows are arranged from the left to right and from bottom to top:

[Image: wings_windows_layout.png]


The wings_frame.erl module is the one where the main window (top_frame) is constructed and the sub-windows are created/loaded/stored.
The docked windows are related to the split record which will always define the way the frame (wxMiniFrame) will be splitted (vertically or horizontally) and the two windows docked (win1 and win2). All float windows are related to the loose record:

[Image: wings_frame.png]


The wings_wm.erl module manages all the events related to the windows in Wings3D as well as it "keeps" the windows list (wm_windows):

[Image: wings_win_geometry.png]


All sub-windows are created in the same way, but the Geometry one is handled in a different way by the wings_wm.erl module:
[Image: wings_win_outliner.png]

[Image: wings_win_palette.png]

[Image: wings_win_sel_group.png]

[Image: wings_win_tweak.png]

[Image: wings_win_views.png]

[Image: wings_win_snap_image.png]]]> wxWidgets library as the new UI (user interface). Maybe it can be useful to any (future) new coders too.
Not all controls/events/functions - available in the wxWidgets library - are exposed to us by Erlang. To know what is available we can check the help page for wx module.

In this layout we can see the way the windows are stored in the preferences file as well as how they are constructed in the memory. The windows are arranged from the left to right and from bottom to top:

[Image: wings_windows_layout.png]


The wings_frame.erl module is the one where the main window (top_frame) is constructed and the sub-windows are created/loaded/stored.
The docked windows are related to the split record which will always define the way the frame (wxMiniFrame) will be splitted (vertically or horizontally) and the two windows docked (win1 and win2). All float windows are related to the loose record:

[Image: wings_frame.png]


The wings_wm.erl module manages all the events related to the windows in Wings3D as well as it "keeps" the windows list (wm_windows):

[Image: wings_win_geometry.png]


All sub-windows are created in the same way, but the Geometry one is handled in a different way by the wings_wm.erl module:
[Image: wings_win_outliner.png]

[Image: wings_win_palette.png]

[Image: wings_win_sel_group.png]

[Image: wings_win_tweak.png]

[Image: wings_win_views.png]

[Image: wings_win_snap_image.png]]]> <![CDATA[emacs setup]]> https://www.wings3d.com/forum/showthread.php?tid=2614 Sun, 21 Jan 2018 19:42:08 +0000 nigec]]> https://www.wings3d.com/forum/showthread.php?tid=2614 Is it possible to get it to show errors in the code? I'm used to C# and Visual Studio which finds errors straight away.
is it possible to include.... "include("wings.hrl")." paths?
I'm using Win10
C:\wingsdev
C:\wingsdev\emacs
C:\wingsdev\src\wings]]> Is it possible to get it to show errors in the code? I'm used to C# and Visual Studio which finds errors straight away.
is it possible to include.... "include("wings.hrl")." paths?
I'm using Win10
C:\wingsdev
C:\wingsdev\emacs
C:\wingsdev\src\wings]]> <![CDATA[Erlang Run Time Errors]]> https://www.wings3d.com/forum/showthread.php?tid=2421 Thu, 02 Mar 2017 21:06:38 +0000 oort]]> https://www.wings3d.com/forum/showthread.php?tid=2421
I am back to playing with converting the Stereoscopic patch to a plugin.

Still working with Wings 1.4.1, since that was where I had already started.

How do we read the information in the error that is generated?

I get an undef error, which is described as follows: "The function cannot be found when evaluating a function call."

How do we know which function is the problem and what does the rest of the information in the report mean? See report below.

Thanks,
oort

Quote:wpc_stereoscopic:command/3: bad return value: {'EXIT',
{undef,
[{wings,geom_title,[{geom,2}]},
{wpc_stereoscopic,
new_viewer,6},
{wpc_stereoscopic,
new_viewer_stereo,1},
{wpc_stereoscopic,command,2},
{wings_develop,time_command,
2},
{wings_plugin,command,3},
{wings,raw_command_1,3},
{wings,raw_command,4}]}}
]]>
I am back to playing with converting the Stereoscopic patch to a plugin.

Still working with Wings 1.4.1, since that was where I had already started.

How do we read the information in the error that is generated?

I get an undef error, which is described as follows: "The function cannot be found when evaluating a function call."

How do we know which function is the problem and what does the rest of the information in the report mean? See report below.

Thanks,
oort

Quote:wpc_stereoscopic:command/3: bad return value: {'EXIT',
{undef,
[{wings,geom_title,[{geom,2}]},
{wpc_stereoscopic,
new_viewer,6},
{wpc_stereoscopic,
new_viewer_stereo,1},
{wpc_stereoscopic,command,2},
{wings_develop,time_command,
2},
{wings_plugin,command,3},
{wings,raw_command_1,3},
{wings,raw_command,4}]}}
]]> <![CDATA[Build error under Arch Linux]]> https://www.wings3d.com/forum/showthread.php?tid=2409 Sat, 18 Feb 2017 06:04:41 +0000 haawda]]> https://www.wings3d.com/forum/showthread.php?tid=2409
build() {
LANG=C
export ESDL_PATH=$(echo /usr/lib/erlang/lib/esdl-*)
make -C "$_pkgname-$pkgver" all lang
}

This does not work:

make: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5'
WINGS_VSN = 2.1.5
(cd intl_tools; make)
make[1]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
make TYPE=opt common
make[2]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
erlc -Werror +debug_info +debug_info -o. tools.erl
escript gen_char_hrl
make[2]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
make[1]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
(cd src; make)
make[1]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
make TYPE=opt common
make[2]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_lang.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin user_default.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_align.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_body.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_camera.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_cl.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_cc.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_cc_ref.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_collapse.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_color.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_console.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_deform.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_develop.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_dialog.erl
wings_dialog.erl:15: can't find include lib "wings/e3d/e3d_image.hrl"
wings_dialog.erl:1593: record e3d_image undefined
make[2]: *** [Makefile:168: ../ebin/wings_dialog.beam] Error 1
make[2]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
make[1]: *** [Makefile:149: opt] Error 2
make[1]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
make: *** [Makefile:15: all] Error 2
make: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5'
==> ERROR: A failure occurred in build().
Aborting...

I did not build the dependencies myself but tried the packages Arch Linux provides.]]>
build() {
LANG=C
export ESDL_PATH=$(echo /usr/lib/erlang/lib/esdl-*)
make -C "$_pkgname-$pkgver" all lang
}

This does not work:

make: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5'
WINGS_VSN = 2.1.5
(cd intl_tools; make)
make[1]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
make TYPE=opt common
make[2]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
erlc -Werror +debug_info +debug_info -o. tools.erl
escript gen_char_hrl
make[2]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
make[1]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/intl_tools'
(cd src; make)
make[1]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
make TYPE=opt common
make[2]: Entering directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_lang.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin user_default.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_align.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_body.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_camera.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_cl.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_cc.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_cc_ref.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_collapse.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_color.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_console.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_deform.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_develop.erl
erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa ../intl_tools -o../ebin wings_dialog.erl
wings_dialog.erl:15: can't find include lib "wings/e3d/e3d_image.hrl"
wings_dialog.erl:1593: record e3d_image undefined
make[2]: *** [Makefile:168: ../ebin/wings_dialog.beam] Error 1
make[2]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
make[1]: *** [Makefile:149: opt] Error 2
make[1]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5/src'
make: *** [Makefile:15: all] Error 2
make: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/wings3d/src/wings-2.1.5'
==> ERROR: A failure occurred in build().
Aborting...

I did not build the dependencies myself but tried the packages Arch Linux provides.]]> <![CDATA[Spanish Translation]]> https://www.wings3d.com/forum/showthread.php?tid=2407 Thu, 16 Feb 2017 18:27:28 +0000 Asticles]]> https://www.wings3d.com/forum/showthread.php?tid=2407
Just finished Spanish translation, made a Pull request, but manually from the web because my repository at github does not update from changes on my local repository (followed Micheus tutorial).

Also, I would like to change es-ES form language menu to Español(España)

Can anybody help me? Tongue

Thanks!]]>
Just finished Spanish translation, made a Pull request, but manually from the web because my repository at github does not update from changes on my local repository (followed Micheus tutorial).

Also, I would like to change es-ES form language menu to Español(España)

Can anybody help me? Tongue

Thanks!]]> <![CDATA[undefined parse transform 'tools']]> https://www.wings3d.com/forum/showthread.php?tid=2329 Thu, 05 Jan 2017 12:55:50 +0000 kugelfang]]> https://www.wings3d.com/forum/showthread.php?tid=2329
When I try to compile wpc_collada.erl (and other plugin sources) --after changing paths to point to the correct included sources from my working directory-- I keep getting this error: 'undefined parse transform 'tools''.

so I follow the includes:
-include_lib("wings-2.1.4.1/src/wings.hrl"). ->
-include("../intl_tools/wings_intl.hrl") ->
-compile({parse_transform,tools}).

And I look at the Erlang reference manual to find that :

Quote:{parse_transform,Module}

Causes the parse transformation function Module:parse_transform/2 to be applied to the parsed code before the code is checked for errors.

Now what? Seems to me that 'parse_transform' is part of Erlang itself, not part of Wings. Has there been a change in Erlang/OTP 19 that causes this error?

Thanks,

--jeff]]>
When I try to compile wpc_collada.erl (and other plugin sources) --after changing paths to point to the correct included sources from my working directory-- I keep getting this error: 'undefined parse transform 'tools''.

so I follow the includes:
-include_lib("wings-2.1.4.1/src/wings.hrl"). ->
-include("../intl_tools/wings_intl.hrl") ->
-compile({parse_transform,tools}).

And I look at the Erlang reference manual to find that :

Quote:{parse_transform,Module}

Causes the parse transformation function Module:parse_transform/2 to be applied to the parsed code before the code is checked for errors.

Now what? Seems to me that 'parse_transform' is part of Erlang itself, not part of Wings. Has there been a change in Erlang/OTP 19 that causes this error?

Thanks,

--jeff]]> <![CDATA[draw more colored edges plugin]]> https://www.wings3d.com/forum/showthread.php?tid=2311 Sat, 24 Dec 2016 08:52:49 +0000 ggaliens]]> https://www.wings3d.com/forum/showthread.php?tid=2311
Very often I find myself wanting colored edges. And I have written and re-written just this plugin a few times. Last time I looked at it all ... the drawing requirements had changed enough so as to invalidate my plugins quite a bit.

So I am here asking for (wishing for) professional help. Maybe from Dan.

I think this particular plugin would make a good "learning" plugin. Certainly has potential to be very simple plugin.

I miss programming in Erlang.]]>
Very often I find myself wanting colored edges. And I have written and re-written just this plugin a few times. Last time I looked at it all ... the drawing requirements had changed enough so as to invalidate my plugins quite a bit.

So I am here asking for (wishing for) professional help. Maybe from Dan.

I think this particular plugin would make a good "learning" plugin. Certainly has potential to be very simple plugin.

I miss programming in Erlang.]]> <![CDATA[Minimum dev environment for plugins...]]> https://www.wings3d.com/forum/showthread.php?tid=2281 Wed, 07 Dec 2016 11:35:39 +0000 kugelfang]]> https://www.wings3d.com/forum/showthread.php?tid=2281
Does the version of Erlang make a difference? I have '1:16.b.3-dfsg-1ubuntu2.1' available in my package manager (I'm using Linux Mint) but I'm assuming this is not the most current version.

Thanks,

--jeff]]>
Does the version of Erlang make a difference? I have '1:16.b.3-dfsg-1ubuntu2.1' available in my package manager (I'm using Linux Mint) but I'm assuming this is not the most current version.

Thanks,

--jeff]]>