[Bf-committers] More editmode problems

[Johnny Matthews]

Please don't wait for me to move ahead on any of that code, I am in
the middle of a hopeful job transition and doubt I will be doing much
coding for a little while. I am working extra hours and by the time I
have free time to code, I am shot for the day.

The % loopcut code was some of my first code written for Blender so I
was just getting the structure down. There is no suprise that it is
deficient. The same goes for vertex loop select. If anyone were to
write better code and completely supplant my code, I would not be
upset in any way, shape or form. I'm just glad I was able to write
some code that worked for a while.


On Mon, 27 Sep 2004 12:48:34 +0200, Ton Roosendaal <ton at blender.org> wrote:
> Hi,
> 
> Yah, I didnt dare to touch loop code yet... it's a hog. :)
> Fortunately, now we have proper edge and face selection awareness in
> Blender, we can make the tools simpler.
> 
> - I prefer no sublooping for select anymore, but directly allow a
> loop-selection on a mouseclick.
> - Based on selection (like rows of edges, faces) you then invoke the
> looping tools, like loopcut for example. Wings has more nice editing
> options we can look at, like the 'slide' tool which moves a selected
> row of edges to the left/right row of edges.
> 
> -Ton-
> 
> 
> 
> 
> On 27 Sep 2004, at 05:50, Alexander Ewering wrote:
> 
> >
> > As I've now ported the new editmesh stuff (still think it's
> > incredible) to
> > instinctive2, I'll be pestering the list with problem reports ;)
> >
> > I know this is work in progress, I'm just providing pointers to
> > possible
> > problems that could be forgotten.
> >
> >
> > 1) It is possible to select edges in face mode by using the
> >    ALT-B (edgeloop select) function. Nothing will indicate that
> >    an edge loop is selected, but grabbing will result in it being
> >    transformed.
> >
> > 2) Both faceloop tools (SHIFT/CTRL-R) do not respect the
> >    zbuffered selection mode and instead also select occluded
> >    loops (in contrast to ALT-B, which works correctly)
> >
> > 3) Apart from this, all the loop functions (ALT-B, SHIFT/CTRL-R)
> >    are badly implemented in that they use 100% CPU even while not
> >    moving the mouse. They should be event-driven, like transform()
> >    appearently is, as it doesn't use CPU while not moving the mouse.
> >
> > That's all for now :)
> >
> > | alexander ewering              instinctive mediaworks
> > | ae[@]instinctive[.]de   http://www[.]instinctive[.]de
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at projects.blender.org
> > http://projects.blender.org/mailman/listinfo/bf-committers
> >
> >
> ------------------------------------------------------------------------
> --
> Ton Roosendaal  Blender Foundation ton at blender.org
> http://www.blender.org
> 
> 
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
> 



-- 
Johnny Matthews
johnny.matthews at gmail.com