Fresco: Android Studio 2.2.2 After the introduction of the XML version of the 0.10.1 property without prompt

[bjxunpai]

Android Studio 2.2.2 After the introduction of the XML version of the 0.10.1 property without prompt
http://share.weiyun.com/678deb081fceabb0f111400eca9c0d13

[kirwan]

Sorry, I'm not sure what you're asking. I wouldn't expect Android Studio to auto-suggest the Fresco custom properties.

Just to note: you've called the namespace "fresco" but this will provide all properties defined in your app or other libraries you use.

[bjxunpai]

when I use the Fresco 0.10.1，there appears the custom property. But when I use the Fresco 0.14.1，no custom property prompts. How can I solve this problem?

[shenjingfs]

Same use Android Studio 2.2.2, I want Android Studio to auto suggest Fresco custom properties, not just the following：

• Fresco 0.10.0
  
  
• If I use Fresco 0.14.1，Android Studio auto suggest a new property：
  
  

Or should I ask questions on Stack Overflow？

[kirwan]

The actualImageUri attribute was added more recently than 0.10.0 so it's no surprise that doesn't appear if that's the version you're using.

I've just found this Stack Overflow question about losing custom attribute autocomplete. If that's what you're experiencing, there are a couple of suggested answers.

[bjxunpai]

https://cloud.githubusercontent.com/assets/12003831/19923314/b01d735a-a121-11e6-85fd-e492e96ac939.png

[shenjingfs]

Thank you for your help. I have seen this problem, and in my Android Studio auto complete looks working:

There are only 4 suggestions in Fresco 0.14.1 when I edit XML:

but I want all of the custom properties.for example,I want to input fresco:progressBarImage,but auto-suggeset only show:

[kirwan]

I've just checked attrs.xml and can see that's because that is the only attribute declared against SimpleDraweeView.

The others are declared against GenericDraweeHierarchy. That can be changed so that auto-complete works, by declaring the attributes against both.

I can't promise when that will happen and would also welcome a pull request.

[dongbingliu]

this problem has solved？

[kirwan]

Not yet. As I said in my previous comment, it would be quite a straightforward pull request for someone though if you can't wait for us to get to this.

[oprisnik]

I believe this should be fixed with v1.4.0, which we released earlier today.