LiveCode Forums

@stam: Sorry - I made a mistake in my code example - it should be `stack "com.livecode....". The handler sits in one of the behavior scripts which make up the Script Editor - the actual code itself isn't specific to an SE instance or anything so it can be used by other things, its just that to call ...

@stam: There isn't an 'official' IDE API for this - although if you post a request to the RQCC about it we can probably add one pretty easily as the code which does the indentation in the SE was exposed to work for the snippet manager we added in LiveCode 8 (?) [ and also so we could write unit test...

@marksmithhfx: If possible, could you file a bug report with sample stack showing this behavior? Something doesn't sound quite right here as taking a snapshot of the screen shouldn't require *camera* access (if user permission is required - then it should be more specific - although this does sound ...

@SimonKnight: The terminal environment is not quite the same as that which you get when you launch an app from Finder (i.e. dock, desktop, folder) by double-clicking. Environment variables are inherited from their parent processes - when you launch from Terminal, a LiveCode app will inherit the term...

So `the XMLHead` custom property of your main stack contains a string which contains U+FFFD (essentially the 'unknown character' unicode character) at the place you were expecting three bytes. So why that is there, rather than what you expected, depends on how you set that custom property. Its worth...

So I can't say for sure what was going on in your case as I don't know what your original code was doing (I've tried to reproduce the effect you described and cannot). Prior to 7 there was no difference between binary data and text - they could be the same because text was only ever single-byte valu...

How is tXMPhead being constructed? It looks like you are mixing text and binary data. Since you are constructing a binary file, you need to make sure that all parts are binary to stop the engine applying default conversions from text to binary (in particular 'invalid' chars will map to ?). If you do...

That'll tide us over well until Microsoft switches to the Linux kernel. :) Once they complete that the Unix philosophy of "everything is a file" will give us a path to the Recycle process that can be used with normal file I/O calls, like the Linux /proc folder provides. #DayDreams I think this is m...

The polygon does not have to have a closed border to be opaque - its just that the engine (whether helpfully or not - depending on your point of view) will implicitly 'close' the points of a 'polygon' when you set the opaque to true (or edit the points property): You can avoid this though - create y...

I'm familiar with file systems. The question is why Microsoft exposes a virtual file path that can't be used? They obviously decided to solve the problem in a slightly different way - and provide a different end-user experience: https://devblogs.microsoft.com/oldnewthing/20110830-00/?p=9773 The key...

Serious question: why does Microsoft provide a path to the Recycle Bin if it can't be used?

macOS does too - its at ~/.Trash (I think there are also folders related to Trash on each read-write volume as well).

The files-which-you-might-want-to-recover have to be stored somewhere!

@no1g8tor96: I posted a further update on the bug report if you could take a look when you get a moment that would be great. I'm still not sure what the issue is exactly (as the IDE runs) but at least we've made some progress, i.e. specifically confirming it is to do with the print subsystem - and m...

So @jwkuehne's example here is simply (when reduced to the minimum required): on mouseUp repeat forever put "foo" into field 1 end repeat end mouseUp Now the actual example we got had 9 fields, and each one was having `the seconds` put into them on each iteration of the loop... However, the seconds,...

@dunbarx: No - it was due to suggesting the order was important - which it isn't if all your handlers are named differently (order *only* matters if you are using handlers with the same name and pass). I think what Stam was asking was whether a handler in backscript can call any handler in any other...

@stam: I think Craig's characterization may be slightly misleading... Whenever a message is sent to an object, the message flows through the message path - first through the front scripts, then to the object targetted by the call, then up the ownership chain, then through the backscripts - the front...