• Paint: paints a soft selection using the magnet brush selected and the magnets route strategy;
  
• Paint from selection: paints a soft selection using as source any regular selection existent;
  
• Paint from weight map: paints a soft selection using as source a greyscale or a coloured weight map (red->blu) uvmapped to a selection;
  
• Erase: the paint mode is switched to erase and any soft selection will be erased using the magnet brush setting as it works for paint mode;
  
• Clear paint selection: clear any soft selection painted;
  
• Magnets->Route strategy:
  • Shortdist: the default Tweak's route mode and it must be the preferred one;
    
  • Surface: this option allow us to paint only one continuous surface when we have other surfaces of the same object close to that one and we don't want it to be painted. As it requires more complex validations it spends more time. So, it's not recommended we keep it the default option if we are working with a high resolution mesh.

• isn't available in Body selection mode;
  
• is disbled and any soft selection is cleaned if Magnet or Tweak is turned off;
  
• Paint and Erase command can be 'hotkeyed' as the other Normal, Scale, Slide... commands;
  
• takes in account any Magnet Lock we have set;

(09-06-2017, 06:20 PM)Asticles Wrote: Thanks micheus, do you think the problem is because of erlang? Should wings be ported to any other major language?

(04-09-2016, 07:47 AM)dgud Wrote: Ok long random rant..

Sigh, I hate this Erlang discussion, that pops up from time to time, if you worked on S-Geometry you know LISP and you know why functional languages is nice to program in.

Erlang is what makes Wings3D as stable as it have been, how many real crashes and bluescreens have you had in these years, and most of these crashes have been dependent on the OpenGL drivers anyway.

Now that I have started to rewrite the gui in wxWidgets (which is a C++) library, and I promise you we will get more random crashes, which will be really hard to debug. Which is really sad but we need to bump the looks from 1999 to 2010 :-)

We have started to require OpenGL 2.0 (which is really old now) to modernize and optimize that part of
the code and we get complaints that Wings-2.0.X does not work for some users.

Some more comments about performance, when Wings was designed in 1999, a model of 1500 faces was about the largest models made and not workable in wings. So Wings ground design was not made to handle 10000 faces or above, we cut corners to make it possible to develop as a one man made project,
which it still is more or less, i.e. performance have never been prioritized and until we have 10 developers that collaborate on a large re-write that will never happen.

Erlang is really good at using multi core systems, actually one of the best languages for doing that type of programming, though Wings was made before multi-core systems existed and need a lot of work to become partly concurrent. Google WhatsApp and Erlang for one example!

What Wings3D need is one (or two) young great developer with lots of time and energy not old dorks that needs to sleep at night. Programming takes time (at least for me), the last two months I have coded wings at least 30 hours per week, that is after my normal work hours, so you can guess what my wife thinks of me, I'll soon be kicked out the house. But for me right now coding wings is fun, next month I will be tired of wings and something else is fun and I will do that instead.

Remember this is a hobby for us.