Fri, Oct 11
Fixed in two commits:
It appears the bug has been fixed already.
Can't reproduce bug in latest builds. Bug was in 2.80.
@Charlie Jolly (charlie) Do you agree this is a not supported feature, no?
@Jacob Bihl (Kurenai) Not sure I understand your request, but when you draw a curve and then you use the eraser, you are changing the tool, so the handles are hidden. If you select the curve again, you never will get again the handles because the curve tool is not designed in that way (this is not a vector drawing software). The curve tool handles are only visible the first time you make the curve.
Thu, Oct 10
Proposed Fix: D6045
@Germano Cavalcante (mano-wii) I have a fix, but not sure if this can be done with less lines:
All the added properties that were missing in the active tool panel seem to work fine
IMHO, as this is not a critical issue, we can include in master for 2.82
Still, is possible to add those fill options also to the active tool in properties editor or this is an automatic thing?
@Antonio Vazquez (antoniov) That's right. Not enough space. I checked and same applies to TOPBAR_PT_gpencil_primitive.
Reverted the DEG_id_tag_update() line.
Fixed code styles and discarded BLI_map.h changes.
Code style fixes.
Wed, Oct 9
Hi, don’t know every much about code and I'm fairly new to blender, can anyone help me out with an explanation on how to fix this issue or which blender scripts to change, I'd very much appreciate it. Thank you!
I'm not sure about flushing the queue where you suggest. handleTabletEvent() does not seem to modify the event in the queue, it just sets some tablet parameters (pressure, tilt) in some window context object, and then presumably some other code uses that info when it comes to processing the event. For drawing, then, you want the latest tablet info available when the event gets processed or else you're always using old pressure data. The only instance where you don't want tablet data smashing is on the leaving proximity event because it leaves tablet mode, and no drawing is going to happen anyway.
can conform this fix works also on astropad and duet.
thanks @Tim Lesher (tim) Carroll (codrus) for this!
@Brecht Van Lommel (brecht) Van Lommel (brecht) is there any reason why this fix can't go in master?
Good catch. I was looking for something like dispatchEvents() yesterday but couldn't find it.
Tue, Oct 8
This may or may not be an acceptable fix, but adding dispatchEvents() when leaving proximity in handleTabletEvent() flushes out the event queue and fixes the issue for me in both grease pencil and texture paint modes:
I can confirm that if I comment out tabletPoint and tabletProximity in WindowCocoaView, the problem goes away. The mouse up messages have tablet information so pressure get released as appropriate. This was just a test; those events are important for tablets with proximity sensors. Also, I found that later events (like window deactivation) were showing tablet events, which would clearly not be the right thing.
I've got a partial answer for what's going on -- will try to pick this up again tomorrow night, but thought I'd pass on some notes.
The same issue happens in the release version of Catalina with Sidecar and an iPad Pro/Apple Pencil.
Mon, Oct 7
This report was closed as a duplicate of T57570, is not fixed.
I checked the experimental version as well (blender-2.81-54a9649e2636-macOS) and it seems to still have this issue, so either a fix for this was not yet integrated into 2.81.. or it it was integrated, the fix was not really fixing this issue. :)
I have the same problem with Blender 2.80 on a mac (MacBook Pro / OSX 10.14.6). also the highlight of selected nodes (in composer, material nodes etc) is too thin and hard to distinguish what the selected nodes are. As a matter of fact many lines displayed throughout the Blender 2.80’s UI are too thin, compared to 2.79
Sun, Oct 6
Sat, Oct 5
Thanks for your report, but as this is related to use Blender on entry-level hardware, we cannot consider it as bug due bug tracker policy.
Fri, Oct 4
Thu, Oct 3
We need more exact steps to reproduce the problem, the description is not precise about what to do to make it crash.
Wed, Oct 2
- GPencil: Use DRW_shgroup_call