In T54963#593809, @William Reynish (billreynish) wrote:

@Cezary Szadejko (cez): It's still alive but still waiting for issues to be solved with left click described here: T57918. Now that left click is enabled by default, it's paramount that we tackle these remaining issues anyway, and that will also pave the way for keymaps such as this one.

This keyboard is mandatory for the new blender.
Your work on this is fantastic but this can't be without work on snapping too (so removing the 3d pointer). Please don't forget that

I don't know if it is a bug, or just a feature not yet implemented, but video playback on empty or importing as an image on plan does not work.
Should I report a bug?

really don't like this change, no more features, what's update in 2.8, more is split. split the 3d viewer, split the editor. this not means more features. combine is more useful, ex. less select from drop-down list. one editor do more things.

@Cezary Szadejko (cez): It's still alive but still waiting for issues to be solved with left click described here: T57918. Now that left click is enabled by default, it's paramount that we tackle these remaining issues anyway, and that will also pave the way for keymaps such as this one.

@Roger B (rboxman), it was not intentional, fixed now.

It looks like some changes to the default startup.blend in recent builds has changed the Auto Perspective default to OFF -- is that by design?

This is great, is this ticket still alive? This is exactly the config I need, could we try it as is?

Yes, that's exactly right. With the UV Editor separate, It makes it possible to add things like UV display or even editing while in Object Mode. It's one of the nice benefits.

Display the UVs very clearly at all times for all 3D Viewport Modes when in the UV Editor

I totally agree with @Julien Kaspar (JulienKaspar) here. I've always found it super annoying that I had to go into edit mode just to see the UVs on a mesh. In object mode, it could even just display them, and only make them editable in edit mode - this would be very intuitive across Blender, and similar to the way Maya works as well, for example.

@Brecht Van Lommel (brecht), that wasn't a kernel/driver version. I've re-installed the entire OS and that did fix the slowness. Not sure what exactly solved the issue, but my guess is that some of the alternatives in ht driver libraries went wrong over the years of initial install.

Is this still something we intend to fix?

The main official addons were ported for the beta, the rest we can do over time or leave to the community.

Alright, I can see that this change is here to stay. No more resistance and no more devils advocate on the current split. There are just a couple of things that I would suggest:

2d Viewport & Image Editor: There's no intuitive connection to any use-case for '2D Editor'. With the UV Editor and Image Editor it's simple and clear. Nobody is confused about what these are for. It's immediately obvious.

If we keep the Editors separate then I like @Brecht Van Lommel (brecht) suggestion and I'd like to try to flesh the idea out a bit.

@Brecht Van Lommel (brecht) Van Lommel (brecht) What if I wanted to paint on the World texture?

As far as I know there are no major changes planned to the UV editor tools and interface, nor does having it as a top level editor or sub mode really affect what can be done.

@William Reynish (billreynish) And I personally agree with all that. It's just that @Julien Kaspar (JulienKaspar) and I had another question that for now remains unanswered:

I am really dying to know the new Tools and interface changes that must be planned to make the UV Editor not just better than it currently is

It's pretty simple: There are more advantages in terms if ease of use when they are split vs combined.

@William Reynish (billreynish) Let's bring up some new arguments please ... or at least reply to the ones from before ;)

The question was: What do we gain from separating them?

@William Reynish (billreynish) To be honest, that's not really answering @Julien Kaspar (JulienKaspar)'s question. And I must admit I've asked the same before. What are the plans for the editors after they've been separated? Any new tools planned, UI revamp, ..?

UV Editor: For editing UVs
Image Editor: For editing the image

@Sam Van Hulle (sam_vh) Right now I don't really care about the question:

@Brecht Van Lommel (brecht) What if I wanted to paint on the World texture? Good idea about separating mesh-related data and independent images. But I still don't see why UV editing and image painting have to happen in the same editor, especially if they're going to limit data access to what is selected in the viewport.
I would suggest this:

• UV Editor: data depends on the selected mesh, allows you to work in a dedicated editor
• Image Editor: independently selected image datablock (you want to be able to paint on anything really), optionally show the selected mesh's UVs. Image Viewer doesn't really need to be something separate. I mean, if you can look at an image, you might as well be able to paint on it without having to open up a different editor.

Thanks @Campbell Barton (campbellbarton) :)

Fixed rB220ab6290e55a67778d6fbf82467a2170fbee413

This is a bug, G to move does not work at all in LMB mode

Confirmed, this only happens when using LMB select.

@Campbell Barton (campbellbarton) It's showing 4 here too.

@Campbell Barton (campbellbarton) Already did it. I will confirm it with tomorrow build. Thanks.

@Fahad Hasan (cgvirus) not sure why you see 'spacebar-4', reset factory settings, set tools as primary action for spacebar in the preferences and it should be spacebar+G.

The RGB values are linear. I would also expect the view transform to be for displaying the colors only. It apparently was changed to fix T39627: HSL color sliders acting funky, but it seems like the wrong solution.

@Brecht Van Lommel (brecht) I would expect the same from the RGB values, no? Only involve the view transform in displaying the colours, not the numbers? I just assumed all of the values were always linear, and wherever I'd see an actual colour displayed, that would have been transformed. Or am I seeing things wrong?