Re: Learning from across the way #10

[richmond62]

Just looked at this:

https://livecode.com/3-great-new-livecode-releases/

Quite apart from feeling that 'great' is not half of what it is cracked up to be, there are 1 or 2 points which might serve us well to think about:

#1 Exporting images to the gif format now works correctly on 64-bit windows

#2 A stack’s visible area will now update correctly when switching between cards when there is a menubar on the stack on macOS

#3 The click command now supports simulating double-clicks

All of those would be super if they could be implemented in OXT.

This strikes me as both funny and odd:

#4 A prototype implementation of the ‘script widgets’ feature has been included (my highlighting)

as LC 10 is supposedly 'the end of the line' why would you insert a prototype something in there, as, presumably, that is as far as the thing will get?

[tperry2x]

Well, none of this is either here-nor-there as far as we are concerned.
I mean, it's a different 'product' now and using a completely web-orientated codebase in create, and as LC10 isn't open source - not much we can learn.
No more than we can really learn from any other product and implement here.
Unless you mean, take inspiration from - but then we have lots of things added that haven't been added 'over there', you just have to look at our release notes and bug fixes.

Having said all that, the double click thing has me thinking 'huh'?

The mousedoubledown message already exists.
Or do they mean: "click at 50,50" - can you now send doubleclick at 50,50?

as LC 10 is supposedly 'the end of the line' why would you insert a prototype something in there, as, presumably, that is as far as the thing will get?

They might be using LC10 as a test bed, even for user reaction, before they implement it in their new 'create' product.

[richmond62]

And exporting a GIF image from the Windows 64-bit version?

[richmond62]

I don't know whether a double-click means:

1. A mouseDown and then a MouseUp.

2. A "clicketty-click" where the user does Down-Up-Down-Up.

As I can put this in a button:

Code: Select all

on mouseDoubleDown
   put "X" into fld "ff"
   wait 2 secs
   put empty into fld "ff"
   end mouseDoubleDown

And on clicking the mouse twice in quick succession an 'X' ends up where it should.

I can, presumably do this elsewhere:

Code: Select all

send "mouseDoubleDown" to btn "B1"

[tperry2x]

And exporting a GIF image from the Windows 64-bit version?

I don't know about Windows, but I already do that on Linux here.
There's probably a windows equivalent command somewhere, I'm sure.

[richmond62]

Yeah, well:

Code: Select all

export snapshot from image "MyDaftPicture" to file "MDP.gif" as GIF

has ALWAYS worked for me on Linux, Mac, and Windows XP: so I assume that was screwing up on Windows 64-bit.

[tperry2x]

Yeah, well:

Code: Select all

export snapshot from image "MyDaftPicture" to file "MDP.gif" as GIF

has ALWAYS worked for me on Linux, Mac, and Windows XP: so I assume that was screwing up on Windows 64-bit.

That only exports a single still frame though of a snapshot, not all the frames.

They probably mean:

Code: Select all

export image "MDP" to file "MDP.gif" as GIF

Doesn't export all the animated frames, just whatever frame the gif is on when you run the export script. I'm assuming they fixed it so it now exports the entire animation.

[richmond62]

Well, I for one am not going to see that as a fantastic advantage.