On 02/24/2018 03:08 PM, Ali Lloyd via use-livecode wrote:
The VCS-related use case for an expanded properties property still exists
though, as far as I can tell, although 'properties' is kind of a bad name
for it. Actually I think it might be better to add 'export' syntax for
classic controls. T
hh wrote:
>> Richard G. wrote:
>> What's missing is support for the universal method by which we can
>> obtain property info, "the properties" function.
>
> In order to work with a widget you have to know what the single
> properties do.
That is true of all objects of all properties.
> I can't
Ali Lloyd wrote:
> Not much has changed since this question was last asked:
> http://lists.runrev.com/pipermail/use-livecode/2015-October/219630.html
So it seems, hence my question. :)
> The question here really is what you want to use the properties
> property for.
My interest this morning c
@Ali... I’ve been mulling over the very idea of extending the export
mechanism. What I would propose is to add an $object key that would contain
the engine related things required to recreate the widget. The same could
be done for any LC object (using $kind to identify the classic
control/object ty
> Richard G. wrote:
> What's missing is support for the universal method by which we can
> obtain property info, "the properties" function.
In order to work with a widget you have to know what the single properties
do. I can't see what should be the purpose of such a "full list".
> Given that t
Not much has changed since this question was last asked:
http://lists.runrev.com/pipermail/use-livecode/2015-October/219630.html
The question here really is what you want to use the properties property
for. It is not correct to say that the properties property is used to
create the property inspec
hh wrote:
>> Richard G. wrote:
>> I'm suggesting the engine have an enhancement to add
>> the widget-specific info to the universally-supported
>> "the properties" info.
>
> It would be possible to simply add all the info that the property
> inspector can display. But that can also easily be scr
> Richard G. wrote:
> I'm suggesting the engine have an enhancement to add the widget-specific info
> to the universally-supported "the properties" info.
It would be possible to simply add all the info that the property inspector
can display. But that can also easily be scripted by the user of th
I just got around to trying this -- *very* useful, thanks for posting it.
There are no matches for any of my passwords I've tried so far. :) On
the other hand, even "AbrahamLincoln" has 128 matches. And you have to
insert commas to read the number returned for "qwerty".
On 2/22/18 10:50 PM, B
Hi Tim,
I am not sure if the DirectShow player (with is the API used by the LC
player on Windows) supports negative playrate:
https://msdn.microsoft.com/en-us/library/windows/desktop/dd377591(v=vs.85).aspx
There is also a bug report about it:
http://quality.livecode.com/show_bug.cgi?id=19129
B
Brian Milby wrote:
>> > Brian M. wrote:
>> > One other thing that could be done is to extend the export to
>> > include everything that the engine knows about the widget (i.e.
>> > add the properties array to it).
>>
>> The widget author can already do that by defining a list of
>> persistent pro
Now I’m really confused:
put the properties of widget id 1004 into tA
Results in an empty tA. If I put something into tA[“rect”] and then set the
properties to tA then it does move to that rect. Is that just my 2
computers (Mac and Win10)? I checked 9DP11 and 8.1.7 (will get the latest 8
now thou
> > Brian M. wrote:
> > One other thing that could be done is to extend the export to include
> > everything that the engine knows about the widget (i.e. add the
> > properties array to it).
>
> The widget author can already do that by defining a list of persistent
> properties. Why should the engi
Navigator has been updated to include:
-- Filtering in the Stack List (both using the filter field, and the more
robust filter command).
-- A fix for an issue where editing properties could show the editor in
HTMLtext mode, meaning that properties would be set incorrectly.
-- A new Save All com
> Richard G. wrote:
> When we query the properties of any object, we get an array that lets us
> understand and even reproduce that object easily.
>
> Except with widgets.
>
> When we query the properties of a widget we get only the subset of
> properties common to all widgets, but none of the
I meant “does”
To get what you want (if different than above) would require something
defined within each widget to export the desired internal information.
One other thing that could be done is to extend the export to include
everything that the engine knows about the widget (i.e. add the properti
Doe this get what you want:
export widget to array arrayVar
On Sat, Feb 24, 2018 at 10:01 AM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> When we query the properties of any object, we get an array that lets us
> understand and even reproduce that object easily.
>
> Ex
When we query the properties of any object, we get an array that lets us
understand and even reproduce that object easily.
Except with widgets.
When we query the properties of a widget we get only the subset of
properties common to all widgets, but none of the properties unique to
any given w
Hi Peter,
Tried
if pkeyname is "j" then
set the playrate of player videoplayer to -1
start player videplayer
end if
Results in a pause in playback as long as I am holding ctrl-j, as
soon as that's released, forward play resumes.
Thanks.
Tim
On 2018.02.25 0:26, Peter Bogdanoff via use-livec
Tim,
Try both commands in order: set playRate, then start.
Peter Bogdanoff
> On Feb 24, 2018, at 10:16 AM, Tim Selander via use-livecode
> wrote:
>
> Hi Paul,
>
> Using 9.0 dp11 community. After sending the post, I found in the dictionary
> that for windows, commandkeydown message. After ch
Hi Paul,
Using 9.0 dp11 community. After sending the post, I found in the
dictionary that for windows, commandkeydown message. After
changing my script from controlkeydown to commandkeydown, it
worked. Sort of.
My next problem is that on the LC/osx I use:
if pkeyname is "j" then set the pl
controlKeyDown is absolutely available on Windows. See the dictionary
entry in LC8.1.9 for example. What version of LiveCode are you using?
On 2/24/2018 9:04 AM, Tim Selander via use-livecode wrote:
> Hi,
>
> Trying my first little LC app on Windows. I wrote an app on osx and am
> now trying to g
Hi,
Trying my first little LC app on Windows. I wrote an app on osx
and am now trying to get it to work in a Win7 machine.
On the mac app, I use ctrl-J, ctrl-K, and ctrl-L to control the
video player. JKL is pretty standard video player control in
video editing software.
On the mac app, th
Hi Tim,
> Am 24.02.2018 um 14:06 schrieb Tim Selander via use-livecode
> :
>
> Hi,
>
> Trying to simply play an h264 video on LC 9 in a player on a Win7 machine.
> Quicktime installed.
> I have .mov, .mp4, .mv4 videos that all play fine on Mac osx /and/ in QT on
> the Win7 machine.
> But I ca
Hi,
Trying to simply play an h264 video on LC 9 in a player on a Win7
machine. Quicktime installed. I have .mov, .mp4, .mv4 videos that
all play fine on Mac osx /and/ in QT on the Win7 machine. But I
can only get .wmv to play in the LC player object on Win7.
Have to create a little in-house
25 matches
Mail list logo
