I'm just now testing your module out and trying to wrap my head around the workflow with regards to Image Styles, suffixes, etc.
I've found that when I create a base Image Style, we'll say "thumbnail", after I've created 5 suffixes in resp_img, I then use the /admin/config/media/resp_img/create_style "Add responsive style" automator to clone the "thumbnail" style, but find that only the largest suffix receives the cloned Effects set up in Image Styles for "thumbnail" and all the other suffixes Image Styles created by the automator have no Effects in Image Styles. Also, the original "thumbnail" Image Style now no longer has any Effects listed under it's settings either.
Is this normal? Honestly I haven't gotten to testing it out but it seems odd that it would steal Effects and only display Effects on the largest suffix Image Style. I expected it to firstly, not mess with the Effects for "thumbnail" at all, as it states it will "clone" that Style, and secondly I'd expect it to clone the same style into every suffix Style to make it faster to then alter any scaling Effect or other Effect needed for a particular suffix.
I realize this feature/functionality was just added recently but before I go and take the time to do this for 20+ Image Styles where I'm guessing I'll have to duplicate styles (and replace those styles in the original Styles since they're deleted) for 5 suffixes making at least 100+ Image Styles and days of work, I just wanted to make sure that there wasn't some kind of hidden coding Effects in those Image Styles created by the Add Responsive Style tab/page form. I'm thinking not since they don't show up in the Effects list nor would it make sense to not be able to touch/alter those Effects (or add what I think should be there from the "cloning") since that wouldn't allow customization of size, etc. for each suffix version of a Style.
Any advice or documentation/tutorials that might shed some light on this process? I also gather from another issue related to "colorbox size" that I should select the smallest version when choosing a style and I guess that the resp_img module will automatically replace it with a larger suffix Image Style if the window is larger? FYI, there really isn't anything anywhere that tells a developer which Image Style should be chosen and what the module does from that point to use the other suffix versions. This would be helpful since it is a departure from the tried and true imagecache/Image Styles method of only being able to choose one style in most module's dropdowns/UI's. The tutorials in the README.txt and on the project page help lay things out but with this automator things got a little hazy when the produced Image Styles didn't end up with any Effects yet had their sample images that looked like stretched versions of the original Image Style "thumbnail"'s sample image, leading one to think some effect was stretching/scaling them but not being listed.
Though it may not have much to do with my question/issue, these are the Suffixes that I'm using, from smallest to largest in order to match-up with AdaptiveTheme's breakpoints:
- Phone Portrait (-phone_portrait)
- Phone Landscape (-phone_landscape)
- Tablet Portrait (-tablet_portrait)
- Tablet Landscape (-tablet_landscape)
- Standard (-standard) [*]
These are the Image Styles after the automation:
- thumbnail-responsive-standard [*THIS ONE ENDED UP WITH THE "CLONED" EFFECTS SETTINGS FROM THE ORIGINAL IMAGE STYLE]
These are the Image Styles Effects that were removed from the original Image Style "thumbnail" and cloned to "thumbnail-responsive-standard":
- Change file format Convert to: png
- Focus Scale And Crop 64x64 medium strength
- Rounded Corners
Thanks for your time and any help! I'll probably go ahead and start duplicating Effects in the suffix Image Styles just to keep development moving forward but any insight would be appreciated as I'm not sure if it's a bug or I'm not understanding how the systems work together. If I can get this working together with AdaptiveTheme it'll allow me to create responsive images that I need that are not full window width as quite a few other modules allow (but I can't image anyone not needing both at some point).