[Staff Post] Use Case Question For Widget Users (Scrollview Related)

Solar2D Widgets
#1

Hi!

 

I have a question for you all. (Please vote for your choice in the thread poll!)

 

When you are creating a scrollView and defining it’s scroll width and height (ie the scroll area of your scrollView) do you want to do this, or should these properties be removed and the scrollView do the hard work for you.

Currently the scrollView will automatically adjust it’s scroll width/height according to added content (there may still be some kinks in this…) if you insert your content directly into the scrollView.

 

Is there any use case for manually setting the scroll width/height yourself? If you manually set the scroll width/height, should the widget library not dynamically update it’s scroll area with added content?

 

Let me know.

#2

I often want to fix the width but let the Height be determined dynamically. So i would suggest that if it is nil in the declaration that you would have the widget determine it dynamically if it is set to a specific size then you would honor that.

#3

Just for clarification, are there 4 parameters: height, width, scrollHeight and scrollWidth? You are only talking about getting rid of the last 2?

#4

Just add the option that if you don’t specify them it’s calculated based on content size… this way we’ve the two options (define it or not), but please close the definition of ScrollView asap, I’m experiencing problems scrolling it… :frowning:

#5

Yea … i think Maxtrix and I are on to how it should work. Lets say we are voting for the undocumented 3rd choice in your poll.

#6

 

Getting rid of or setting how it is used, as was suggested. 

 

 

Please create a new thread if you are having scroll difficulties and I will assist.

 

 

The option you both suggested sounds good to me, I just want to ensure everyone is on the same wavelength so there is no confusion. 

PS: I added that option to the poll

#7

“Please create a new thread if you are having scroll difficulties and I will assist.”

 

It is created already : -> Scroll Not Scrolling, few days ago already… :slight_smile:

#8

I often want to fix the width but let the Height be determined dynamically. So i would suggest that if it is nil in the declaration that you would have the widget determine it dynamically if it is set to a specific size then you would honor that.

#9

Just for clarification, are there 4 parameters: height, width, scrollHeight and scrollWidth? You are only talking about getting rid of the last 2?

#10

Just add the option that if you don’t specify them it’s calculated based on content size… this way we’ve the two options (define it or not), but please close the definition of ScrollView asap, I’m experiencing problems scrolling it… :frowning:

#11

Yea … i think Maxtrix and I are on to how it should work. Lets say we are voting for the undocumented 3rd choice in your poll.

#12

 

Getting rid of or setting how it is used, as was suggested. 

 

 

Please create a new thread if you are having scroll difficulties and I will assist.

 

 

The option you both suggested sounds good to me, I just want to ensure everyone is on the same wavelength so there is no confusion. 

PS: I added that option to the poll

#13

“Please create a new thread if you are having scroll difficulties and I will assist.”

 

It is created already : -> Scroll Not Scrolling, few days ago already… :slight_smile: