Rotor does everything I need it to, until it comes to using it in Views and I'm unable to get the width settings to act how I want.

First of all, I think they are completely unnecessary. Anyone who needs to alter the style or dimensions of the rotating node should learn to use CSS and Views theming. That's just my opinion.

Second, it limits those who theme their Views by placing the dimension styles inside the tag by default, rendering theme classes and id's useless.

e.g. <img class="imagefield imagefield-field_screenshot" height="600" width="800" src="http://cteaguedesign.com/portfolio/sites/default/files/man_1024768.png?1248583589" alt=""/>

Third, without any values in the rotor items' height and width (again, as a Views style), it defaults to some tiny set of dimensions.

Finally, I wouldn't even have these problems if I could just make my rotor items' height and width to 100%.

Any way to fix these issues, now or in a future release, would take this module to the next level. As it is, it's extremely frustrating to use the Rotor as a Views style.

Comments

g10tto’s picture

g10tto commented

Oops, wrong tag. That'll teach me to proofread my support requests. :P

This is the code I was referring to in the second point.

<div class="rotor-content" style="position: absolute; top: 0pt; left: 0pt; display: none; z-index: 2; opacity: 0; width: 108px; height: 1238px;">

g10tto’s picture

g10tto commented

bump

g10tto’s picture

g10tto commented

those of us who forgot their basic CSS learnin' raise their hands. *raises hand*

sorry to make a stink, I forgot about the all-important "!important" tag.

g10tto’s picture

g10tto commented
Status: Active » Closed (fixed)
mrfelton’s picture

mrfelton commented

The width setting is provided for convenience, as is the Rotor Item content type. Many people find this useful (those that do not want to have to dive into code of any kind just to get a rotating banner on their site). So, I'm reluctant to remove the setting. Unless someone can convince me otherwise. I understand that you may like to use css to control the style - who doesn't. However, I'm not quite clear why you can not achieve the width you need by setting it in the view, or why it was totally neccessary to do this in css in the first place. The only reason I can think of is if you want to use the same view display on two different pages, each showing at a different size..?

Perhaps, I could make it so that a width/height of 0/0 removes the hardcoded sizes from the generated code?

g10tto’s picture

g10tto commented

That's a good solution. But it would still leave the issue of a lack of 100% width or height for those who don't want to dive into the code.