LiveCode Forums.

It's not documented, but I have seen that "the result" of "close printing" and the "print" commands appears to be empty on success, and "printing failed" when I send too much at it. Can I depend on the result from these, as in checking for empty to be a good result? How about "open printing..."? Tha...

Maybe related to?

http://quality.livecode.com/show_bug.cgi?id=17362

Love the project browser. Just turn off "Show thumbnails"

I must admit I prefer the v7 disctionary to the v8 one. Haven't really played with v8 one to tell about other things. Although on Windows the project manager doesn't seem to persist across restarts. Widgets are awesome tho.

Disregard, already confirmed:

http://quality.livecode.com/show_bug.cgi?id=16496

I was wondering if anyone has seen any issues with the postgres external lib (dbpostgresql.so) provided in LC 7.1.3/4 on Linux64. I'm using Fedora 21 and whenever I attempt to connect to the database I get a "revdberr, invalid database type" error. If I copy over the postgres library from the 7.0.6 ...

@jacque: Thanks for the feedback. I'm using a similar workaround, but as you can imagine this lessens the usefulness of empty params if they don't propogate and behave as you would expect 'empty' to.

@-hh: Ha! Seems I'm late to the party. Thanks for the link.

The problem I am facing with it is how it propagates through functions. If I do Something(Something()) then again it will be equal to 0. This can cause unexpected outcomes when you think an empty parameter should equate to empty. Also, this will continue even if you assign it to a variable such as: ...

on mouseUp
answer Something() = 0
answer Something() = empty
answer Something(empty) = 0
answer Something(empty) = empty
end mouseUp

function Something pNothing
return pNothing
end Something

This will return
'true'
'true'
'false'
'true'

Is this expected?

@LCMark: Thanks for the reply! Good to know I'm not crazy I will do as you say but it may be some time before I can get this together. Need to get my project released in the next week or two. Thanks again!

What about just making all the grid pieces buttons? Then you can toggle them when they hit them and also present a graphic background.

Looking through the livecode open source project some, the openSockets function is a representation of MCsockets. To read/write a socket, the code looks up the connection id given by a user in MCsockets, say "127.0.0.1:4400" and finds the first entry in the list that matches it. It uses this descrip...

Yes, computers are deterministic, therefore the livecode openSockets function was designed with an intent. Was the intent to allow duplicate entries? Anyway, I'll get some code to review, but it will be a couple of weeks. I've worked around the issue by using another list to track the sockets in use.

It seems rather odd that there is no definitive answer on whether the livecode function openSockets should have duplicates or not. I will gladly pare down my code to something I can post to the forums in the meantime, but it would be nice to know if this should even occur. I asure you nothing nefari...

No updates? Perhaps someone could answer this question: Should livecode ever have duplicate entries in the openSockets list? I would think not, since these describe the peer connections, which should always be unique. Otherwise, how could you know who you were communicating with using read from/writ...