[Bf-viewport] reporting 2.80 pre-bugs

[Dalai Felinto]

Hi Mike,

I think it's fine for developers to report them, though it's still early
for users to do it. (In other words, we can't afford to spend time with
triaging, but it's fine to use phabricator to keep track of known issues).

As long as we tag the issues as 2.8 it should be fine.

And if I may add to this list, the new manipulator code that was merged
still has plenty of deprecated calls :/. Not sure if it was addressed in
one of the manipulator branches. But it's the kind of "regression" that is
worth keep track of.

Regards,
Dalai

On Apr 9, 2017 03:07, "Mike Erwin" <significant.bit at gmail.com> wrote:

> On Windows all the new features are available for testing. I'm really
> enjoying the new transform manipulator & new wireframes together at last!
>
> A few issues I noticed:
> - rotation manipulator crashes on Mac (clipping plane issue similar to
> T51143 -- I can fix this one too)
> - visual feedback during rotation does not always start where I click
> (would feel more "solid" if it matched the cursor)
> - scale manipulator causes button outlines to disappear (OpenGL state
> issue?)
> - placing the 3D cursor with Clay & Eeevee causes all UI outside the 3D
> view to go blank. Mouse over a blank region and it will redraw.
>
> Should we use Phabricator to report pre-release bugs? They must be
> reported somewhere so we can all track what needs more work.
>
> Mike Erwin
> musician, naturalist, pixel pusher, hacker extraordinaire
>
> _______________________________________________
> Bf-viewport mailing list
> Bf-viewport at blender.org
> https://lists.blender.org/mailman/listinfo/bf-viewport
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-viewport/attachments/20170409/5e71111b/attachment.htm