Widget properties

Is it not a bug that the properties of widget “foo” returns empty (for all values of foo)? No rect, no visible, no disabled etc, even though these clearly are settable and functional properties of the widget. You can export widget “foo” to array “bar” but that gives the intrinsic pr

Re: Widget properties

That is not available according to this post from Ali Lloyd https://forums.livecode.com/viewtopic.php?t=27183#p141945 > Am 06.04.2022 um 14:03 schrieb Neville Smythe via use-livecode > : > > Is it not a bug that > > the properti

Re: Widget properties

Forgot to mention that his post also has a solution to fetch the list of all available properties for a widget. > Am 06.04.2022 um 14:36 schrieb matthias_livecode_150...@m-r-d.de: > > That is not available according to this post from Ali Lloyd > > https://forums.livecode.com/viewtopic.php?t=27

Re: Flash Talks - 3 slots remaining

So is this a video that I make beforehand and upload somewhere, or is it usually meant to be a live show? Craig > On Apr 5, 2022, at 8:28 PM, Ralph DiMola via use-livecode > wrote: > > Me too. > > Ralph DiMola > IT Director > Evergreen Information Services > rdim...@evergreeninfo.net

Re: Widget properties

That post from Ali says they are not available; it doesn’t say they should be not available. I’d say they should be - Ali’s workaround is good for the IDE only. So no reason not to submit as a bug/request, and get a proper determination from LCLtd. Alex Sent from my iPad > On 6 Apr 2022, at

drawingSvgCompileIcon(pIconName) always BLACK

Hi all, drawingSvgCompileIcon(pIconName) is really great, but the resulting images are always black. I can of course add a "color overlay" but when I use them as "imagesource" it uses the original black images. Any hints on how to add color to them when using them as "imagesource" in a field wi

Re: Widget properties

Maybe. But the last 6 years no one filed a bug report, even Ali did not. So i doubt, that it will be fixed in the near future even with a bug report. Anyway, without a bug report there is definitely no chance that it will be ever fixed. > Am 06.04.2022 um 15:22 schrieb Tweedly via use-livecode

Re: Flash Talks - 3 slots remaining

Very often you will make the presentation beforehand and make yourself available to answer any questions at the time of presentation. I guess Heather will guide you through the process. Best regards Tore Nilsen > 6. apr. 2022 kl. 15:12 skrev Craig Newman via use-livecode > : > > So is this a

Re: drawingSvgCompileIcon(pIconName) always BLACK

Just made a test and it looks like the resulting images from drawingSvgCompileIcon(pIconName) cannot even be screenshot-ted!? Results in a greyish rectangle? WTF? Tried as PNG and JPEG. see screenshot here: > Am 06.04.2022 um 15

Re: drawingSvgCompileIcon(pIconName) always BLACK

Bug reported it: > Am 06.04.2022 um 15:35 schrieb Klaus major-k via use-livecode > : > > Just made a test and it looks like the resulting images from > drawingSvgCompileIcon(pIconName) cannot even be screenshot-ted!? > Results in a greyish re

Re: Widget properties

I would suggest filing a report and get the ball rolling. If you reference in the post by Ali and your other workarounds it will at least be useful to some and at best provide information that leads to a fix. On Wed, 6 Apr 2022 at 14:30, matthias rebbe via use-livecode < use-livecode@lists.runrev.

Re: drawingSvgCompileIcon(pIconName) always BLACK

Sounds a little like the old bug where a PNG would draw as black if it had an Alpha channel. Bob S > On Apr 6, 2022, at 06:23 , Klaus major-k via use-livecode > wrote: > > Hi all, > > drawingSvgCompileIcon(pIconName) is really great, > but the resulting images are always black. > > I can

Re: drawingSvgCompileIcon(pIconName) always BLACK

The IDE supports importing SVG images from the Import As Control menu. Does that work any differently? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On April 6, 2022 8:36:29 AM Klaus major-k via use-livecode wrote: Just made a test

Re: drawingSvgCompileIcon(pIconName) always BLACK

Hi Jaques, > Am 06.04.2022 um 17:59 schrieb J. Landman Gay via use-livecode > : > > The IDE supports importing SVG images from the Import As Control menu. Does > that work any differently? not tested (yet). > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http

Re: drawingSvgCompileIcon(pIconName) always BLACK

> Am 06.04.2022 um 18:10 schrieb Klaus major-k via use-livecode > : > > Hi Jaques, > >> Am 06.04.2022 um 17:59 schrieb J. Landman Gay via use-livecode >> : >> >> The IDE supports importing SVG images from the Import As Control menu. Does >> that work any differently? > > not tested (yet).

Re: drawingSvgCompileIcon(pIconName) always BLACK

Hi all, so sorry, looks like I completely f. up here. Sorry for the confusion, not may day... See: Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de __

Re: drawingSvgCompileIcon(pIconName) always BLACK

On 2022-04-06 18:16, Klaus major-k via use-livecode wrote: Hi all, so sorry, looks like I completely f. up here. Sorry for the confusion, not may day... See: Hehe - no worries. So in answer to your original query about wanting to be ab

Re: drawingSvgCompileIcon(pIconName) always BLACK

On 4/6/22 11:13 AM, Klaus major-k via use-livecode wrote: Am 06.04.2022 um 17:59 schrieb J. Landman Gay via use-livecode: The IDE supports importing SVG images from the Import As Control menu. Does that work any differently? not tested (yet). just tested and THAT works!? There must be more

Re: drawingSvgCompileIcon(pIconName) always BLACK

Hi Jaques, > Am 06.04.2022 um 20:48 schrieb J. Landman Gay via use-livecode > : > > On 4/6/22 11:13 AM, Klaus major-k via use-livecode wrote: Am 06.04.2022 um 17:59 schrieb J. Landman Gay via use-livecode: The IDE supports importing SVG images from the Import As Control menu. >>

Re: drawingSvgCompileIcon(pIconName) always BLACK

I guess I need to make an update to this library :) Sent from my iPhone > On Apr 6, 2022, at 1:28 PM, Mark Waddingham via use-livecode > wrote: > > On 2022-04-06 18:16, Klaus major-k via use-livecode wrote: >> Hi all, >> so sorry, looks like I completely f. up here. >> Sorry for the confu

Re: drawingSvgCompileIcon(pIconName) always BLACK

Hi Brian, > Am 06.04.2022 um 21:18 schrieb Brian Milby via use-livecode > : > > I guess I need to make an update to this library :) yo, that would be cool! :-) > Sent from my iPhone > >> On Apr 6, 2022, at 1:28 PM, Mark Waddingham via use-livecode >> wrote: >> >> On 2022-04-06 18:16, Klau

Re: Widget properties

I suspect this will be classed as not a bug as there has never been any intention of supporting the properties for widgets as far as I’m aware but it might be worth submitting it anyway and detailing your use case. I think if you look at the old lcVCS discussions on the forums from before my tim

Re: Widget properties

Monte Goulding wrote: > ...there has never been any intention of supporting the properties > for widgets as far as I’m aware... If the company wants widgets to be seen as first-class citizens, a little more conformity with existing object syntax would go a long way to making that happen. It'

Re: Widget properties

Poor Widget. The bastard child of Livecode objects. ;-P Bob S > On Apr 6, 2022, at 16:39 , Richard Gaskin via use-livecode > wrote: > > Monte Goulding wrote: > > > ...there has never been any intention of supporting the properties > > for widgets as far as I’m aware... > > If the company w

Re: widget properties

I have submitted the bug report (Bug 23670 ) As others have said, it is not likely this will be considered a high priority bug but it should be on the record. Interestingly eg setting tbar[“textcolor”] to a value and then set the properties o

Re: Widget properties

> On 7 Apr 2022, at 9:39 am, Richard Gaskin via use-livecode > wrote: > > Monte Goulding wrote: > > > ...there has never been any intention of supporting the properties > > for widgets as far as I’m aware... > > If the company wants widgets to be seen as first-class citizens, a little > more

Re: Widget properties

On 4/6/22 16:39, Richard Gaskin via use-livecode wrote: > ...there has never been any intention of supporting the properties > for widgets as far as I’m aware... If the company wants widgets to be seen as first-class citizens, a little more conformity with existing object syntax would go a l

Re: Widget properties

Monte Goulding wrote: > It seems a stretch to imply the lack of support for a property that > has little to no use case outside the IDE means the company doesn’t > take widgets seriously but I’m not going to argue with you about that. A reasonable choice, given that "seriously" is a colloquialis

Re: Widget properties

Mark Wieder wrote: > On 4/6/22 16:39, Richard Gaskin via use-livecode wrote: > >> > ...there has never been any intention of supporting the properties >> > for widgets as far as I’m aware... >> >> If the company wants widgets to be seen as first-class citizens, a >> little more conformity with

Re: widget properties

Just a point of clarification; Ali’s post does not explain how to access the object properties of a widget. The properties returned by put the keys of (revIDEExtensionProperties("com.livecode.widget.foo")) are the intrinsic properties of the widget, which these days are accessible via the e

Re: Widget properties

> On 7 Apr 2022, at 11:25 am, Richard Gaskin via use-livecode > wrote: > > > I will say there’s two main use cases for `the properties` and neither > > of them it serves very well: > > > > - Getting the properties of an object to apply to recreate the object > > elsewhere. export widget does a

Re: Widget properties

At the conference I will announce a plugin, which will have the code read and write widget properties. The code for the plugin will be on github. I'm insanely busy at the moment, so I can't accelerate the release. No magic, just hardcoded property names. :) On Wed, Apr 6, 2022 at 10:08 PM Monte Go

Re: widget properties

On 4/6/22 19:04, Neville Smythe via use-livecode wrote: Unfortunately LC doesn’t respond with a “object does not have this property” error message if you query any old reserved property key for a widget. It's actually even worse. The clock widget, for instance: The exported array contains spec

Re: Widget properties

Thank you for your reply, Monte. Comments inline: Monte Goulding wrote: >> On 7 Apr 2022, at 11:25 am, Richard Gaskin wrote: >> Can you help me understand how it's better than "the properties", >> and why this superior method isn't used for engine controls? > > Because the array created by export