Page MenuHome

GPencil – Selecting Stroke Points With Selection Tools Not Possible
Closed, InvalidPublic

Description

System Information
Operating system: Linux-5.3.0-42-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.59

Blender Version
Broken: version: 2.83 (sub 11), branch: greasepencil-object, commit date: 2020-03-26 12:17, hash: rBe12d75af8c12
Worked: (newest version of Blender that worked as expected)

Short description of error
In the branch greasepencil-object it is not possible to select more than one points of a stroke in Edit Mode with Lasso Select and Box Select tools. And therefore it is not possible, to delete, move, or scale them.
It is possible to select one or more points with LMB and Shift+LMB.
It is also possible to select points with the Circle Select tool.

Exact steps for others to reproduce the error

  1. Open Blender (greasepencil-object branch) and select 2D Animation
  2. Draw a line or whatever
  3. Press Tab to switch to Edit Mode
  4. Press 1 (the number) to change the Select Mode to Points
  5. Press B to activate the Box Selection Tool and try to select some points.

–––––––––––––––

You are awesome, btw. :)

Event Timeline

ronsn created this task.Thu, Mar 26, 3:44 PM
ronsn added a project: Grease Pencil.

I cannot reproduce. Can you try with the last master compilation (the greasepencil-object branch is now alpha again, not stable).?

Antonio Vazquez (antoniov) changed the task status from Needs Triage to Needs Information from User.Thu, Mar 26, 6:35 PM
ronsn added a comment.EditedThu, Mar 26, 7:42 PM

@Antonio Vazquez (antoniov) The last master does not have this issue. But I have to go into Default Workspace and add a GPencil object to test it because of T75112.

May I do a short screen cast to show, how the issue looks like?

Edit: I made a screen cast^^

Antonio Vazquez (antoniov) claimed this task.

I see the problem now. Anyway, I'm going to close the task because due phab policy, only bug reports for master branch are allowed.

@ronsn If you want tell me bugs about branch (it's very useful for us), just contact with me by chat or twitter or mail.

ronsn added a comment.Fri, Mar 27, 2:52 PM

@Antonio Vazquez (antoniov) I didn't know about that policy. I read Bug Reports but couldn't find anything about those policy :/ I mean everyone talks about such a policy but I never understood what it means :D Could you give me a hint, or a link where I can read the policy?

But besides that, if it's better for you to handle, I could contact you via chat, or email (I don't have Twitter, because they want my telephone number) :)

I mean, BF Blender is supposed to only be for Official Blender Foundation releases (that includes the BF Build Bot that builds master as this will eventually become a release).
There are numerous tasks for branched features and development, and those don't have the tag, but are pretty much exclusively made by developers.

ronsn added a comment.EditedSat, Mar 28, 5:46 AM

@Christopher_Anderssarian If that tag is only supposed for official Blender Foundation releases, than we could just remove the tag "BF Blender" afterwards (which is there by default but can be removed after committing a report)!

My issue is, that I don't get a clear statement, what is a bug report and what is not a bug report "by policy". Where is that policy? Maybe I'm stupid, but I didn't find any. (And I bet, I'm stupid :D)
And btw. the greasepencil-object branch was an "official" build bot branch a few weeks ago.
Sorry, but I can't know all. I have to develop other software for other people and can't track all changes here, but I try to give my part as a volunteer to Open Source back, because I learned a lot of it.
I mean: "bisecting" takes a lot of time. Making clear reports takes time. Being responsible for a report takes time... That's it, what I can give, but without a clear "policy" it can become frustrating :D

Please, can anyone give me a link to that policy?

Another question: How did you remove the brackets after your name? :D

than we could just remove the tag "BF Blender" afterwards

True, but this has multiple issues, mainly that there's enough to do in master as it is and if the tracker was officially opened up to all branches less time would be spent on code that is part of the release cycle. Also it wouldn't necessarily get triaged, but I digress...

My issue is, that I don't get a clear statement, what is a bug report and what is not a bug report "by policy". Where is that policy?

I would argue it's the first bullet point under Please verify:

Experimental vs. Official. It depends on what you're using as a basis for a build's status, I guess it could be made clearer.

And btw. the greasepencil-object branch was an "official" buildbot branch a few weeks ago.

I said master, don't you sneakily pull one over me ;)

Please, can anyone give me a link to that policy?

Well, here is where the answer came from.

Another question: How did you remove the brackets after your name? :D

You can remove your "Real Name" then it displays just the user name.

ronsn added a comment.Sun, Mar 29, 5:48 AM

than we could just remove the tag "BF Blender" afterwards

True, but this has multiple issues, mainly that there's enough to do in master as it is and if the tracker was officially opened up to all branches less time would be spent on code that is part of the release cycle. Also it wouldn't necessarily get triaged, but I digress...

Okay, but can everyone open a new branch inside this "official Blender versioning system"?
If no: Than we could remove the BF Blender tag.
If yes: You are right.

My issue is, that I don't get a clear statement, what is a bug report and what is not a bug report "by policy". Where is that policy?

I would argue it's the first bullet point under Please verify:

Experimental vs. Official. It depends on what you're using as a basis for a build's status, I guess it could be made clearer.

True. It's not clear. Let's use this statement in the next statement:

And btw. the greasepencil-object branch was an "official" buildbot branch a few weeks ago.

I said master, don't you sneakily pull one over me ;)

:D Yes, but I only want to hug you :D
But for real: If it's only the master-branch, than one can't say

[...] and daily build from builder.blender.org

because greasepencil-object branch is one of those "daily build[s] from builder.blender.org".

Please, can anyone give me a link to that policy?

Well, here is where the answer came from.

Okay, I tried it in several browsers. Result:

Another question: How did you remove the brackets after your name? :D

You can remove your "Real Name" then it displays just the user name.

Thank you again! I changed it. Thank you! You are awesome, btw. :)

Okay, but can everyone open a new branch inside this "official Blender versioning system"?

I'm not sure what you mean here. What I feel.

Okay, I tried it in several browsers.

Probably just need to login into blender.chat.

Okay, but can everyone open a new branch inside this "official Blender versioning system"?

I'm not sure what you mean here. What I feel.

I wasn't sure how to call the official Blender repositories and forks, that is why I quoted myself. :D

Okay, I tried it in several browsers.

Probably just need to login into blender.chat.

Okay, I'll look into that later. But it looks like a bug anyway^^

ronsn added a comment.Mon, Mar 30, 3:59 AM

@Christopher_Anderssarian Opening your link to blender,chat resulted in the same issue: Loading...
Hoever, I was able to get logged in and the answer was:

[The issue should be closed] as invalid indeed, but you can open a devtalk thread for feedback on whatever feature you are working on, and then you point users to that thread if they want to report their findings during tests

That is more like a request, but not a policy :/
I give you an example: A month ago (or so) I asked how to handle bug reports that are written in languages other than in English. There was no rule for it so someone changed the introduction text on the BF Blender Bug Report page that bug reports should be made in English only. Now this statement is gone.
It seems to be that there is no policy at all, but only arbitrary statements about a fictive policy.
That would be meaningless for me personal, if I gave an advise or made a decision about an issue. It would be a foggy forest full of opinions without clear instructions, which can become really frustrating.

I want a policy! Now! I'll sign a petition and until that I'll protest! xD

But seriously – even if I'm really ironic – Is there any chance to get a link to that rules or to the policy of bug reporting?

:)