Fixed
Status Update
No update yet.
Comments
pe...@gmail.com
I believe this is for the shim library but it's unclear who the new owner is now, so please triage and reassign.
lb...@gmail.com
@2 You'd better not use beta 2 , too. It has other issues.
lb...@gmail.com
@4 Seems so. Thanks.
Are there any known issues on beta 4?
Are there any known issues on beta 4?
ni...@google.com
The only issue so far we've heard is 146413738 -- likely some problem with NestedScrollingParent3. If you find other problems please do file them. Thanks!
lb...@gmail.com
@6 Thank you.
Currently the bugs that I know about it, is in the IDE, of almost always not being able to convert other layouts into it, properly.
Currently the bugs that I know about it, is in the IDE, of almost always not being able to convert other layouts into it, properly.
ni...@google.com
Conversion should work, albeit may not be a perfect one (unless you convert from relativelayout, where iirc we can provide that). If you have examples you could file of problematic conversation that would help us. Thank you!
lb...@gmail.com
@8 There are plenty of ways to show it.
And I've already reported some. Here's one of the recent ones, which shows it can't handle even the most simple example: a LinearLayout with TextView and ImageView :
https://issuetracker.google.com/issues/145311069
This is why I never use this feature of conversion. It's way worse than converting to Kotlin. For conversion to Kotlin, at least I got a workaround to make it work better: always add nullability annotations.
For ConstraintLayout , it almost never goes well. Doesn't add the constraints, and instead puts junk stuff that I never intended to add and don't even need. Almost never gets something that can even be built.
And I've already reported some. Here's one of the recent ones, which shows it can't handle even the most simple example: a LinearLayout with TextView and ImageView :
This is why I never use this feature of conversion. It's way worse than converting to Kotlin. For conversion to Kotlin, at least I got a workaround to make it work better: always add nullability annotations.
For ConstraintLayout , it almost never goes well. Doesn't add the constraints, and instead puts junk stuff that I never intended to add and don't even need. Almost never gets something that can even be built.
pe...@gmail.com
The barrier issue seems fixed in beta4, but flow doesn't work. I'll make or find a separate issue for that.
pe...@gmail.com
Nevermind, after building the project, the Flow problem was also fixed in beta4 :)
ni...@google.com
:) thanks for checking!
Description
implementation 'androidx.constraintlayout:constraintlayout:2.0.0-beta3'
In the layout editor of the IDE, it doesn't show the barrier well. Instead it's always a gray row at the top.
Android Studio 4.0 Canary 1
Build #AI-192.6817.14.36.5959023, built on October 23, 2019
Runtime version: 1.8.0_212-release-1586-b04 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 7916M
Cores: 12
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins: String Manipulation, ignaciotcrespo.github.com.vector-drawable-thumbnails, com.mistamek.drawablepreview.drawable-preview