You should always base you work/branches of dgud/master
Setup a remote (once)
git remote add dgud git://github.com/dgud/wings.git
For each new branch:
git fetch dgud
git checkout master
git merge --ff-only dgud/master (or git reset --hard dgud/master)
git checkout -B MyName/ChangeDescription dgud/master
The snapshots are based on pu
but the pu branch is temporary i.e. you can build and test it but not base your branch on it, it will be removed and remade each time I update it.
I have fixed the clip_plane crash..
But I got this when testing the new windows (Micheus please fix):
Long stack trace:
[{wings,move_windows,
[[{wpc_views_win,{{plugin,saved_views},
{1825,0},
{144,374},
[{rollup,false}]}},
{wpc_sel_win,{{plugin,sel_groups},
{1826,397},
{144,374},
[{rollup,false}]}}]],
[{file,"wings.erl"},{line,1717}]},
{wings,handle_event_3,2,[{file,"wings.erl"},{line,434}]},
{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}]},
{wings_wm,get_and_dispatch,0,[{file,"wings_wm.erl"},{line,612}]},
{wings,init,1,[{file,"wings.erl"},{line,148}]}]
Dan, I see there are the two new windows info in the same error dump. Please, what were you doing when it happened?
I had a quick look to see what a saved view would be all about. I'll assume this is all brand new. My general impression is that there are too many options presented for such a simple function. I would suggest always add & name at same time. I might have deferred on the rename option for time being. And then delete by name. I'm not seeing need for NEXT. I mean ... it's not going to grow into an animation system , right ?
I think the idea of saved views is great. I'd just start simple simple simple ... because then debugging and learning to use will be simple. The users will give you you next great idea for save views I'm sure.
Also the interface could be simplified if the save view names were on the first sub-menu rather than the second on. And then all the ACTIONS to be performed would be applied to that (perhaps on submenu or info line). Like making it more like window-outliner or window-geometry graph.
Just my two cents.
Micheues: I created both of your new windows, closed wings and restarted it.
I doubt Micheus needs any help finding the bug. But I was trying to follow along. I didn't see the actual ERROR message in the dump listed above.
I'm assuming you guys are speaking of selection groups and save views windows. I opened both did a save and closed and reopened. No bugs yet.
I like both these windows Micheus. Nice. But here is a question ... What would be the down-side of having a single window to control both saved selections and views ? When I want to see a selection ... a particular view would be handy. Certainly you could have a view with no selction. Not a big deal. You could still call it saved views and have people savy enough to "get-it". That would leave a question of what happens when you "union" two saved selections. I would say just pick the view associated with the larger selection.
I found a problem related to the new way to show Tweak Magnet influence area. It happens in the Vertex mode. The Tweak influenced vertices are shown as blue-black squares, varying according the influence. The problem is: when a whole area is being afected by Tweak Magnet, Wing is unable to redraw the work area and, even if user hits "deselect" or makes another vertices selection, that influenced vertices remain as blue squares. Very annoying. It isnt a Tweak problem, but a magnet influenced area DISPLAY problem.
Yet about this new way to show Tweam Magnet influence, specially in vertex mode, why the influenced vertes have so big blue squares? It is difficult to visualizate the geometry with some degree of zoom-out! Wouldnt there be a way to reduce the Tweak Magnet influenced Vertex display?? It isnt confortable as the things are being....
Returning to initial bug i am reporting, here is the video showing the problem. The problem is clear at 1'26", when i deselected all and the blue vertices remained.
http://www.youtube.com/watch?v=E5nWSGYKk...e=youtu.be
ps: all the operations in video are Tweak ones.
Could you developers confirm the problem?
Thanks for the attention.
I've recorded another one to show the problem again.
The only way i found to exit that situation is to select all vertices and apply a Magnet Mask to them (Tools|Magnet Mask|Lock) and then the opposite (Tools|Magnet Mask|Unlock).
About the unconfortable Magnet influenced Vertex display, which squares are too big, i show that in the video at 0'30" by zooming out. Therefore that vertices visualization prejudices model visualization all the time...
http://www.youtube.com/watch?v=-94Av46bg...e=youtu.be
(12-12-2012, 03:26 PM)Fonte Boa Wrote: [ -> ]I found a problem related to the new way to show Tweak Magnet influence area. It happens in the Vertex mode. The Tweak influenced vertices are shown as blue-black squares, varying according the influence. The problem is: when a whole area is being afected by Tweak Magnet, Wing is unable to redraw the work area and, even if user hits "deselect" or makes another vertices selection, that influenced vertices remain as blue squares. Very annoying. It isnt a Tweak problem, but a magnet influenced area DISPLAY problem.
It seems there is something else that I have to take a look.
Thanks for the reply, Micheus.
And what about the way vertices are displayed in the new Tweak Magnet way?
Although 1.4.1 didnt show the degree of influence on each vertice, the visual was cleaner and visualization more confortable.
As i mentioned, the size of vertices are bigger then necessary, occlusing the geometry.
The 3 solutions that i can imagine:
an option in Preferences|General/Edge Display to control that size;
an option in Tweak|Preferences to show or not the magnet influence in the vertices;
a way to turn off that magnet influence display, leaving the things as they were.
I would prefer the second way, because keeping it optional, each user would be able to set the best situation for his purposes.
I know the importance of this for Height Displacement tool you developed, but for box modelling a cleaner interface is better and more important for model visualization.
So please i ask you a way to make that optional: is it possible, Micheus?
EDIT: In few words, Micheus and Optigon, the "blue circle" is good enough to visualize the area influenced by Magnet. And the "blue circle" keeps the object visualization CLEAN. If you really will implement this new visualization, i ask you two an option in Tweak/Preferences to make it optional, please.
please, optigon and micheus... i dont want to have to work with that Tweak Magnet display...
And another annoying aspect of this new magnet display mode: the visual becomes very confuse if i have some Magnet Masks applied on geometry, occlusing this masks quick visualization....
Quote:an option in Tweak|Preferences to show or not the magnet influence in the vertices
Sounds like a good compromise. I like seeing the blue-black colors in the verts, since it helps me to visualize where the magnet influence ends.
oort
I just noticed that Micheus's work on sculpt has not been added to the snapshot release. Will this be added?
oort