LiveCode Forums

@mwieder: lol - with hindsight it probably should have been multiWordCamelCasePropertyNameHell - probably would have illustrated my point better

@mwieder : do you mean the unicode / native stuff? This is only when fetching 'the properties' property, and then only for the 3 or 4 properties that could be unicode or native.

Hi all, This is just to let you all know the release-6.0.1 branch has now been merged into master. Hopefully we've resolved the majority of the build issue, so branching off master should be a little easier now! This release contains a number of bug-fixes and full details can be found in the release...

@FourthWorld - that would, indeed, be me

Ack - looks like I managed to thoroughly confuse myself with this one (mainly by not reading more closely!)... For some reason I though 'controlIds' existed already for some object (card?) hence my vehemence that the immediate children search should be childControlIds. Sorry about that :S So, just t...

Reviewed the code for MCStack::checksharedgroups()... It only iterates over top-level groups and ensures that any that should have the 'shared' bit set do, in fact, have the shared bit set. Its purpose is to ensure that any (top-level) group that is placed on more than one card does have this bit se...

Argh.. I just pushed relying on hasunicode for them all... I know - I had forgotten it was a little more complicated - sorry about that :S I guess that's most likely to be consistent too... any reason I can't move canconverttonative to MCObject? How about an MCExecPoint method. Since properties are...

I changed the setprops method to set style among a couple of other thins first because otherwise it overrides other properties.. Is that what you mean? Yes - that was the main example I had in mind. So hasunicode() means it should return ALL unicode props even if only one has been set to unicode? H...

Ah.. well I think your lockMessages plan is the way to go there... is there anything I need to do to enable that? Well, nothing explicit as it would be in script... e.g. lock messages get the properties unlock messages As I said, this may be something that needs to be reviewed as I'm not 100% sure ...

Hmm... well the sharedBehavior can currently be true on a nested group which is why I sent that other pull request. Even if that's fixed we can no longer rely on it unless when the stackfile loads nested groups get their sharedBehavior set correctly... Ah - indeed - I just found the comment on MCSt...

I meant if it turned out it was a bad idea for 'effective' and 'the properties' to be hung off of overridden getProp handlers (e.g. when you get the effective foreColor, the engine calls getprop() on the parent) then it would require a change to the sites that use getprop() in the engine.

I think it needs to be 'childControl*' for only the immediate children... The reason here is that people currently understand 'control' as recursing, thus 'child control' would restrict to just immediate children (not an ideal situation, granted, but one we have inherited - for now). In regards to s...

@ricochet1k : Yes, we do plan to improve image transformation options since Skia does general 2d affine transformation... Which works quite well with the changes in 6.0 which mean you can effectively do away with using buttons with icons - image data of referenced images (those with filename) are sh...

Hmm... I've got no problem dropping the name, id, layer.. good plan. I'm not sure how I will know if the call is recursing up the object hierarchy for effective though... In general I think if someone has gone to the trouble to script a handler to return something slightly different for a property ...

Hmm... Isn't htmlText a complete representation of styledText? At least in the context I'm using it in it's much easier to work with because I don't need to worry about encoding... for styledText I'd need to parse it for unicode and utf8 it... I do realise it's not just me using this thing and I co...