Closed matthewrdev closed 4 years ago
Following up on this, a suggestion for the BaseSize
attribute.
When the image asset is a SharedImage
and a bitmap, do not require the BaseSize
attribute. The BaseSize
attribute requires that I calculate the correct mdpi resolution, which significantly increases the barrier of entry.
Rather, treat the image as the maximum density version of each platform. Users could then specify a MaximumSize
and Resizetizer would downsample from there.
When building the image importer, I went through several iterations and found that treating an images size as it max density and then downsampling from there was the most intuitive for my users.
@Redth Following up on this (again). Here is IntelliSense, tooltips, analysis and image management support added into MFractor for Resizetizer:
Tooltips
IntelliSense
Analysis
Image Management
Hey thanks for sharing!
The integration looks nice :). I didn’t expect any tooling to integrate with this, so one thing I’m wondering is if you depend on the output path being the same always (eg: inside obj/resizetizer).
I agree for the base size suggestion. This problem is hard to solve nicely but I do look your suggestion and will implement that.
This solves a significant problem and I'd like to support it :)
To support Resizetizer I am inspecting the BuildAction
for a project file then including it into my image asset engine. It's all done using the IDE project model and not the obj output.
Perfect, this is the right way to discover them!
This is all done @Redth, closing this issue.
Hi Redth,
Long time fan, first time caller.
I'm currently adding image IntelliSense, analysis and management support for Resizetizer
SharedImage
s in MFractor.Would you be available to join me in a call to discuss what I can do to further help integrate Resizetizer into Visual Studio Mac? For example, an action to
Add Shared Image
from within the right clickAdd
menu in the solution pad.Let me know :)