[ANN] Working on a Knob Control
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Posts: 632
- Joined: Wed Apr 24, 2013 4:53 pm
- Contact:
[ANN] Working on a Knob Control
"Borrowing" heavily from Trevor DeVore's rotating SVG code, I'm building a new Knob Spinner control LCB Widget. Still in the planning / testing / alpha stage. More or less just testing for posting an animated GIF as a demo here. Apparently there is a very small file size limit for GIF attachments. I can't upload a 328K GIF? Seems a bit ridiculous in the year 2021. Not sure exactly what the limit is but here's a cut down version under 100K:
Last edited by PaulDaMacMan on Sun Feb 14, 2021 7:41 pm, edited 2 times in total.
-
- Livecode Opensource Backer
- Posts: 9444
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: [ANN] Working on a Knob Control
The limit is 256K for each file: this is one of the reasons why my DropBox
thing is bursting at the seams.
thing is bursting at the seams.
-
- Posts: 632
- Joined: Wed Apr 24, 2013 4:53 pm
- Contact:
Re: [ANN] Working on a Knob Control
OK. Thanks for the info Richmond.richmond62 wrote: ↑Sun Feb 14, 2021 7:41 pmThe limit is 256K for each file: this is one of the reasons why my DropBox
thing is bursting at the seams.
-
- Posts: 632
- Joined: Wed Apr 24, 2013 4:53 pm
- Contact:
Re: [ANN] Working on a Knob Control
Slightly Larger, 12 FPS:
Re: [ANN] Working on a Knob Control
PaulDaMacMan wrote: ↑Sun Feb 14, 2021 7:38 pmI can't upload a 328K GIF? Seems a bit ridiculous in the year 2021. Not sure exactly what the limit is but here's a cut down version under 100K:
Speaking purely towards the images, if you have a really large image you want in your post, you don't have to tax your dropbox account, or shrink the image into something that can't be seen at all.richmond62 wrote: ↑Sun Feb 14, 2021 7:41 pmThe limit is 256K for each file: this is one of the reasons why my DropBox
thing is bursting at the seams.
There are a large number of image sharing sites around, some of them better than others depending on what you want to accomplish. For instance, postimage.com lets you not only store an image, but provides you with a number of ways to post it as you can see in this image (which I actually uploaded to imgur.com) -
and the image that picture is a picture of on postimage...
As well, creating an account is free and easy, I have several galleries on postimage and one of those has some of the emoticons I use here, such as
when I want to toast someone ...
-
- Posts: 632
- Joined: Wed Apr 24, 2013 4:53 pm
- Contact:
Re: [ANN] Working on a Knob Control
I've made a bit more progress over the last couple of days.
Here's the gitHub repo: https://github.com/PaulMcClernan/LCB_KnobWidget
One thing I've been stuck on is how to properly mirror LiveCode classic control's Effects panel in the Property Inspector. There are no examples of doing this in an LCB Widget that I could find. I can get some of the dropShadow effects parameters to jive-up, but I don't know how to make the settings all live in the pop-out window they should appear in when the user clicks the "dropShadow" icon in the PI. What happens is the effects parameters all wind up in the main PI window underneath the dropShadow checkbox and icon, and when you click the dropShadow icon you get an empty pop-out window where the dropShadow effects parameters should be. As a work around for now, I've renamed those parameters so that they don't mirror LiveCode's Effects (FYI: apparently "shadow" is a reserved property name, I used outerShadow instead)
Here's the gitHub repo: https://github.com/PaulMcClernan/LCB_KnobWidget
One thing I've been stuck on is how to properly mirror LiveCode classic control's Effects panel in the Property Inspector. There are no examples of doing this in an LCB Widget that I could find. I can get some of the dropShadow effects parameters to jive-up, but I don't know how to make the settings all live in the pop-out window they should appear in when the user clicks the "dropShadow" icon in the PI. What happens is the effects parameters all wind up in the main PI window underneath the dropShadow checkbox and icon, and when you click the dropShadow icon you get an empty pop-out window where the dropShadow effects parameters should be. As a work around for now, I've renamed those parameters so that they don't mirror LiveCode's Effects (FYI: apparently "shadow" is a reserved property name, I used outerShadow instead)