Code-folding boundary line won't be drawn until function is collapsed at least once

[prolium]

After defining a function (without collapsing it) the boundary line of the code-folding won't be drawn:

After collapsing, then expanding it again:

Also when the boundary line is still not drawn, clicking on the function's first instruction would result in the disappearance of the folding icon:

[torusrxxx]

I'm afraid part of this issue won't be added soon. Code folding feature saves each range in a tree. It does not allow overlapping ranges to be folded. The code folding line is drawn only if the code segment is added in the tree. Therefore, you either have to register the range of the entire function in the tree, thus do not allow people fold two functions, or keep it as what it behaves today. As for selecting the first instruction hides the checkbox. Folding of the entire selection is always prioritised. If the selection has only one instruction then the checkbox is hidden because folding a single instruction is a silly operation.

[NHleegong]

In x32dbg Version Feb 23 2020 , if set breakpoint with type == Software ,
it maybe causes error running progress under some case
checksum of these aera is verified in debugged APP Software .
In case of self-extracting codes , if set Hardware breakpoint before the
correct binary code is extracted into breakpoint , debugger does't
responds with short-cut F7/F8/F9 anymore after several F7/F8/F9 steps .