If you restore header, and the tab icon move down again, will work.

Checked again. Need UI scale >1 (have 1.25).

Already looked at this. It feels a bit out of reach for me.

fixed 5a144c797a3b

@Campbell Barton (campbellbarton) I'm almost certain that has to do with the UI: ignore events in empty region overlap areas patches. Although I didn't check previous commit.

In T63835#665262, @Philipp Oeser (lichtwerk) wrote:

Anyways, being able to bring them back easily once hidden sounds important, maybe we should integrate the header menu into the VIEW3D_MT_view [since this is now per editor]?

The problem I mention was fixed, with 5a144c797a3b.

will renaming be a problem? can it break saved keymaps?

I can confirm this. It was the first thing I found when I added footer. And followed header as an example instead of navbar.
I don't remember exactly why this is happening. But has something to do, with navbar added initially for properties. While it was an afterthought for preferences.

@Clément Foucault (fclem) Almost forgot.
Because DRW_cache_free_old_batches runs only when there is a screen refresh, you may want to change this line.

@Clément Foucault (fclem) The problem starts with commit 223f7e79f9 (need the file to replicate).

@Howard Trickey (howardt) This kept coming to my head.
I believe I fixed it (it is working in my eyes).D4719
Is this wrong?

Made a patch D4718.

@Campbell Barton (campbellbarton) I'm guessing the problem is 6aef124e7d28. It was fine with b46245470f79 build.

Oh nice @Yu-sion (Yu-sion), it looks as duplicate of T63698.
I wonder if screen space reflections problem T63512 is also the same.

Duplicate of T63512.

I cannot replicate the problem with the file either (win10 - amd gpu).
But there is a duplicate T63763 for win 7 too.

I can't replicate the problem. (Win10 - amd gpu)
Someone else will test it with mac too.

I'm not dev, just tinkering a bit. I was looking at the cube and thought, 'How was that missed? Looks easy enough"
But I can see the problem, now that you mention it.
For width, maybe, you can take half width from the axis you use for depth towards each point.
But... But... Never mind, it looks impossible to me now.

From what I can tell, grease_pencil was in object or scene in 2.79.
The addon used the objects grease_pencil to stretch the vertices.
Now grease_pencil is a separate object.
The error is exactly that, object has no grease_pencil anymore.
Not sure how the annotation work. Must be in scene?

@Ahmed Badawy (AhmedBadawy) Wait for the new version to be updated with the fix here.
Tomorrow, or the day after should be up.

Not much info to work on.
Do you get any error message?
Is this happening with any blend file? (eg. default cube)
Can you provide a small blend file? So we can try and reproduce the problem.

I can replicate the problem.
@Howard Trickey (howardt) I see, you are working with bevel operator. Maybe you want to look this bug, too.

You are right, this doesn't make sense.
I'm changing the bug status back.
This was a functionality with Multi-edit addon shipped in 2.79.

In case you missed it. But need to be a small file.

This bug has no description of the problem.
But more importantly I don't believe this add-on comes with blender.
Should ask the creator of the add-on for more info.

I just saw the description update.
In 2.79 there was no multi-edit. These objects are 1 joined object and are indeed stretched, as would be in 2.80 if you join them too.
In multi-edit mode are separate objects and as such, there is no stretch.

This is how it should be work. You just resize a separate cube. There is no stretch.
If you join the cubes will see that it working fine.

Did you try the latest version from https://builder.blender.org/download/?
Does it closes immediately? Any error message would be helpful.
It would be nice to know the exact version. It is the filename of the download, or maybe the folder name where you extracted blender.

I'm not a developer, but could not replicate the problem (with amd).
Did you test the latest version? Are your drivers updated?

keeping timeline at the bottom of video editing workspace small.

Somewhat related patch D4714.
Might want to look them together.

Somewhat related patch D4711.
Might want to look them together.

The original problem no longer exist. But it was still used, to keeping timeline at the bottom of video editing workspace small.

@Brecht Van Lommel (brecht) In versioning, you remove multiple headers, instead of RGN_TYPE_FOOTER.

@William Reynish (billreynish) My suggestion is a solution to the search problem, mentioned from

@Pablo Vazquez (pablovazquez) wrote:

If we use a different name in Python it makes it hard to search for it later, since search shows the operator name.

This is good point, also for consistency with the tool's settings panel at the bottom.
But in the search menu there is not enough info(missing popup info too). If someone see 'smooth vectors', will not know about what vectors, this tool is.

made a patch D4663.

@Jacques Lucke (JacquesLucke) @Brecht Van Lommel (brecht)
It looks like a version bump needed with footer.

The file didn't work.
But can confirm, will take a look at it.

Imo "Vectors" word is redundant too.

Done, switched Add with Multiply too.

Faster and improved.

I cannot find a way to keep the old value, expect keeping the userdef->obcenter_dia too.

Style:
Add missing space.
And Moved 1 line down. Versioning line 2987

Revert and the rest of code, that depends on footer been after header.
(1 break for sync_header_alignment)

Tried couple times the workspaces, but don't get any error.

Revert versioning to add footer after header.

I found the problem, but cannot say I know the reason.
No region will work after RGN_TYPE_WINDOW.

Yeah, can confirm. I failed to check that part.
previous diff works fine.
Will try to understand why it stopped working.

Made footer independent from region order.

I looked at ED_area_newspace, it does not seem to be the case, it swap regions and clears old data.

The two issues I still have are about:
a. ED_area_newspace (see the two inline comments added with this comment).

Added ED_area_footersize,
and beautify code a bit.

Update to master.

I totally forgot about the lower bits part you mention.

Before you start review the code, consider this.

I intend to update the patch with the same diff for this part, after you commit D4611.
Just to make sure there is no conflict.

~~~~

Fix style.

Need to fix style.

In D4601#105197, @Brecht Van Lommel (brecht) wrote:

I think the foot appearing on the opposite side of the header is fine.

Moved dist calculation from rectangle, in the else statement.

I should mention a related bug, in case it is a 5 minute fix. But it is such a minuscule issue, that I don't believe opening a bug report worth it (you seem to have enough of these).

@William Reynish (billreynish) As I see it, there is. This patch needs those 3 fixes D4611 to be correct.

improved area_max_regionsize logic

In D4601#104899, @William Reynish (billreynish) wrote:

The updated version seems good to me, using the header theme.

I tried to solve the problem In the two inline comments, and found bugs.
I updated D4611 with the fixes.
If I update this patch, for a proper review, now will need these fixes first. Or it won't run.

Added fix 2, 3.
Clean up more code with the this update.

While this patch fixes more regions, there is still a bug left, I want to fix together. Maybe I will separate the old code removal part into a different patch.

I was referring to the two comments I added in code above.
But that's fine, doesn't matter for now. I don't expect to stay the way it is, right now in this patch.