Need hints how to adapt/hack wings_draw.erl

RSS
Email

0 Kudos

Author	Comment
ggaliens	Need hints how to adapt/hack wings_draw.erl	Lead	[-]
(06/29/09 05:50:27) Reply Quote More My Recent Posts	Tags : None Need hints how to adapt/hack wings_draw.erl I'm sure I can do again since code base has changed (wpc_ogla is gone). I think there is a PREFERRED and legitimate way for plugins to adapt drawing. I want to be able to draw my "directed edges" once again in the current codebase via my plugin(s). My prior approach was to "PATCH" wings_draw, which is of course not the best way. So if one of you devs could drop me some hints / examples of where to look in code to see a good example of how I might adapt drawing and make custom for my plugin, would be appreciated. In mean time ... I'll probably start hackin' and slashin' my way to a better understanding.
optigon		#1	[-]
(06/29/09 06:29:07) Reply Quote More My Recent Posts	You should definitely look at the way wpc_magnet_mask.erl connects with wings to draw masked vertices. I modified a number of core wings files to allow plugins to draw elements more easily. Basically, you want to store your draw elements in the #dlo record under the plugins=[]. You can see how I did this in wpc_magnet_mask.
ggaliens		#2	[-]
(06/29/09 17:36:21) Reply Quote More My Recent Posts	OK ... so I probably just need to export these two ??? update_dlist/3,draw/4 Correct ???
dgud		#3	[-]
(06/29/09 23:44:46) Wings Magician Reply Quote More My Recent Posts	I have rewritten stuff last week as well and exported a couple of new functions, take a look if you need more functions, shout now when I'm inside that part of the code.
optigon		#4	[-]
(06/30/09 07:52:34) Reply Quote More My Recent Posts	ggaliens wrote: OK ... so I probably just need to export these two ??? update_dlist/3,draw/4 Correct ??? -export([update_dlist/3, draw/4, get_locked_vs/1, get_data/3, merge_we/1]). update_dlist/3 compiles the gl list, draw/4 is called from wings_render.erl. I used gl_point, added colour, size, alpha... very basic. merge_we/1 is used to transfer draw data to the proper We when merging/combining/bridging/separating objects. If an object is added to another object, there may be similarly id numbered verts or other elements. So Wings has to renumber all the elements so that each is unique. merge_we/1 ensures that the elements you are storing for your draw elements are renumbered accordingly. get_data/3 There are currently only two atoms/tags/flags that are looked for when wings goes to get the stored data to draw stuff from plugins ('update_dlist' and 'save'). Because the #pst could be used to store all sorts of data, 'update_dlist' or 'save' in the first argument of get_data is there to allow you to specify what data to retrieve from the pst. And specifically, what to redraw/update when usings the 'update_dlist' tag, and what to save with in my_model.wings when using the 'save' tag. get_data/3 is called from wings_plugin.erl as ?MODULE:get_data/3 Also look at the bottom of wings_plugin.erl. There are two functions exported from there (draw/3 and check_plugins/2). But mainly, all you should have to do is store and call element and draw data in the proper format from your wpc_plugin.
ggaliens		#5	[-]
(06/30/09 15:52:35) Reply Quote More My Recent Posts	The data I want to draw is fleeting. I don't expect to have to merge it ... so I'll try not to worry about that yet ... here's what I have so far ... trying to just witness some calls ... even if I don't draw anything. draw(plain, {es,List}, _D, Selmode) -> erlang:display("dedge draw called !"), wings_dl:call(List), ok; draw(_,_,_,_) -> ok. merge_we(_Whatever) -> erlang:display("Merge Whatever !"), _Whatever. update_dlist({es,_ },#dlo{plugins=Pdl,src_we=#we{vp=Vtab}=We}=D, _) -> Key = ?MODULE, erlang:display("Called dedge update_dlist"), List = gl:genLists(1), gl:newList(List,?GL_COMPILE), gl:'begin'(?GL_LINES), gl:vertex3fv({0,0,0} ), gl:vertex3fv({1,1,1} ), gl:'end'(), gl:endList(), D#dlo{plugins=[{Key,{es,List}}\|Pdl]}. get_data(update_dlist, Data, Acc) -> erlang:display("Called dedge get_data !"), {ok, [{plugin, {?MODULE, {es, [ 1 ] }}}\|Acc]}; get_data(save, Data, Acc) -> % the 'save' causes vertices to be renumbered erlang:display("Called dedge get_data !"), {ok, [{plugin, {?MODULE, {es, [ 1 ] }}}\|Acc]}. OK ... I seem to have registered some things I need. Will have to do more hacking to figure out what this API is all about. OK ... I cracked the code a bit. I got something to draw. Neat. Thanks. Last Edited By: ggaliens 06/30/09 16:43:34. Edited 3 times.
ggaliens		#6	[-]
(06/30/09 18:38:15) Reply Quote More My Recent Posts	Yeah !! You da man Optigon. Thanks for helping to work this part of the API out with the DEVS. I got it working. So not too long before another ManifoldLab release.
optigon		#7	[-]
(06/30/09 20:25:49) Reply Quote More My Recent Posts	Glad it worked out for you <<I don't expect to have to merge>> Well just so you know what to expect. If objects with your directed edges are merged, then there will be draw errors unless this part of the api is used.
ggaliens		#8	[-]
(07/01/09 05:47:18) Reply Quote More My Recent Posts	OK ... I'll be sure to delete directed edges as part of the merge. Thanks.
optigon		#9	[-]
(07/01/09 05:57:13) Reply Quote More My Recent Posts	You can do that.. but merge_we/1 will renumber the edges according to the new object, keeping them in the proper place. So there is no need to delete them.
ggaliens		#10	[-]
(07/01/09 16:35:24) Reply Quote More My Recent Posts	Dan ... can you think of something that changed from 1.1.4 to 1.1.5 (presumably last week) that would have broken my first attempt at being draw plugin compatible ??? Works ok in 1.1.4. I'll have to get back in there and do some more studying. Here's a bit of crash dump I get when trying to install my latest ManifoldLab into 1.1.5 ... so maybe you will know what I'm missing , or not doing from this ??? Dump written 2009-7-1_22-10 Version: 1.1.5 Window: geom Reason: function_clause Short stack trace: [{wings_draw,update_needed_fun,4}, {wings_dl,map_1,5}, {wings_draw,refresh_dlists,1}, {wings,main_loop,1}, {wings_wm,handle_event,3}, {wings_wm,send_event,2}, {wings_wm,do_dispatch,2}, {wings_wm,get_and_dispatch,0}] Long stack trace: [{wings_draw,update_needed_fun, [{dlo,none,none,none,none,none,none,none,none,none,none,none,none,none, none,none,none,none,none, {none}, [],false, {we,1,0,"cube1", {array,13,100,undefined, {{undefined, {edge,0,1,5,0,5,3,2,4}, {edge,0,3,0,2,6,1,3,8}, {edge,0,4,2,5,10,2,1,9}, {edge,1,2,3,0,7,5,1,6}, {edge,1,5,5,3,9,1,4,11}, {edge,2,3,1,0,8,7,4,2}, {edge,2,6,3,1,11,4,6,12}, {edge,3,7,1,2,12,6,2,10}, {edge,4,5,4,5,11,10,3,5}}, {{edge,4,7,2,4,8,3,9,12}, {edge,5,6,4,3,12,9,5,7}, {edge,6,7,4,1,10,11,7,8}, undefined,undefined,undefined,undefined,undefined, undefined,undefined}, Last Edited By: ggaliens 07/01/09 18:12:43. Edited 1 times.
optigon		#11	[-]
(07/02/09 08:19:13) Reply Quote More My Recent Posts	Not sure.. the dlo is being wiped clean somewhere. Maybe unrelated, but I had to update to the latest erlang before 1.1.5 would compile properly.
dgud		#12	[-]
(07/03/09 07:45:04) Wings Magician Reply Quote More My Recent Posts	I think I changed a lot :-)
optigon		#13	[-]
(07/03/09 09:00:36) Reply Quote More My Recent Posts	But as far as the api for drawing plugin elements, I don't think anything changed. If there was a problem, Magnet Mask would have stopped working. For the dlo to be blank (as in the error report), there would likely be a problem with your code involving updating the dlo.
ggaliens		#14	[-]
(07/07/09 18:30:16) Reply Quote More My Recent Posts	Optigon, Dan G ... Shouldn't there be a callback into plugin whenever any manifold destructive/constructive operation occurs ??? as opposed to just merge_we ???? How can my plugin be made aware of when a topology destructive operation is going to occur ??? Please advise.
ggaliens		#15	[-]
(07/07/09 18:36:40) Reply Quote More My Recent Posts	My directed edge data is a look up of right faces for each edge. But this expires often when a destructive/constructive operation occurs. So I need to come up with a scheme for letting this info "expire" I could use some kind of CLUDGE like count the faces, verts, edges on the We whenever I attach the directed edge list. But this will likely not be perfect solution.
dgud		#16	[-]
(07/08/09 10:17:01) Wings Magician Reply Quote More My Recent Posts	Keep a copy of the we and diff the edge table for changes between the new and old we.

<< Previous Topic Next Topic >>

Yuku free message boards

Need hints how to adapt/hack wings_draw.erl

Need hints how to adapt/hack wings_draw.erl