Re: Weird button behavior

Thanks for the tips. The breakpoint statement sounds useful, although in this case, I never would have guessed where to put the breakpoint. Unfortunately, they way my code is constructed, the offending statement didn't get executed unless the card was modal. I guess that's another thing to wa

Re: Weird button behavior

On 2/5/11 5:31 PM, Peter Haworth wrote: I just figured out what was going on and I guess it's worth mentioning since it points out the dangers of testing modal dialogs. In the preOpenCard handler for the modal dialog there was this statement: set the width of this card to 425 This, of course,

Re: ClickLine anomaly?

I see. Well, the workaround is easy whichever way it might have gone. In the end this is what matters to me most. Craig -Original Message- From: Robert Brenstein To: How to use LiveCode Sent: Fri, Feb 4, 2011 1:58 pm Subject: Re: ClickLine anomaly? On 04.02.11 at 12:43 -0500 dun

Re: Extended 80-bit hex floating point (IEEE?) conversion

You could easily clean this code up. You could easily make it much shorter and/or faster I just ignored corner cases, error checking, and other cases that probably don't matter to you. I just ignored negative numbers !!! and with all those caveats, try this in your msg box put "400EAC440

Re: Weird button behavior

Peter- Saturday, February 5, 2011, 4:01:52 PM, you wrote: > I was just setting you up for a plug Mark! Thanks for the ...and in that case, I'm falling down on the job. http://www.ahsoftware.net/PowerTools/PowerDebug/PDDemo.html http://www.ahsoftware.net/PowerTools/BuyPowerDebug.irev -- -Mark

Re: Weird button behavior

I was just setting you up for a plug Mark! Thanks for the reminder though, I will now check out PowerDebug. It would have saved me a couple of days of chasing this one down. Pete Haworth On Feb 5, 2011, at 3:51 PM, Mark Wieder wrote: > Pete- > > Saturday, February 5, 2011, 3:31:58 PM, you w

Re: Weird button behavior

Pete- Saturday, February 5, 2011, 3:31:58 PM, you wrote: > So I guess now my question for the community is - What techniques > do you use to test modal dialogs? Well, PowerDebug *does* catch errors in modal dialogs. Debugging modal dialogs is a bit of a tricky situation, though, because the d

Re: Weird button behavior

I just figured out what was going on and I guess it's worth mentioning since it points out the dangers of testing modal dialogs. In the preOpenCard handler for the modal dialog there was this statement: set the width of this card to 425 This, of course, is not a valid statement since cards don'

Re: Weird button behavior

On 2/4/11 7:39 PM, Peter Haworth wrote: Strange thing happening, actually not happening, when I click on a button in a modal dialog window. I have a mouseUp handler for the button with a few lines of code ending with a close this stack statement. The stack closes but setting break points shows

Re: Hex values for Crayola colors

On Sat, Feb 5, 2011 at 1:09 PM, Alex Tweedly wrote: > > For RGB codes do you mean 3 comma-separated byte values, converted to 6 hex > digits ? > > If so, you would use something like > >> put "123,55,255" into aRBG >> put format("%02x%02x%02x", item 1 of aRGB, item 2 of aRGB, item 3 of aRGB) >> in

Re: How to send a number as a number or How to rule an LED

Tom, Yeah, yeah, that's all certainly possible. At last I am getting somewhere, a relaiable connection and communication with the arduino with all kinds of data. At the moment I work on a demo which has 2 sensors attached to the arduino and a led on the arduino >From LC I can send data from a

Re: Weid button behavior(2)

Pete, I'd move your break point up or down a line - or two. Joe Lewis Wilkins Architect & Director of Product Development for GSI On Feb 5, 2011, at 2:04 PM, Peter Haworth wrote: > Still have zero luck trying to track this down. Are there any other possible > ways to trace what's going

Weid button behavior(2)

Still have zero luck trying to track this down. Are there any other possible ways to trace what's going on, give that my debug break point isn't being triggered? Any LC log files, anything like that? Pete Haworth http://www.mollysrevenge.com http://www.sonicbids.com/MollysRevenge http:/

Re: Hex values for Crayola colors

For RGB codes do you mean 3 comma-separated byte values, converted to 6 hex digits ? If so, you would use something like put "123,55,255" into aRBG put format("%02x%02x%02x", item 1 of aRGB, item 2 of aRGB, item 3 of aRGB) into aHex -- Alex. On 05/02/2011 18:12, David C. wrote: Cool lin

Re: How to send a number as a number or How to rule an LED

Hi, I'm not a real big fan of the "muscular morons," but it might improve your opinion of Sylvester Stallone if you were aware that he not only starred in the "Rocky" series, but he wrote and directed too! My family just did an experiment for an exercise in film criticism (acting like critic

Re: How to send a number as a number or How to rule an LED

On 02/05/2011 08:21 PM, Thomas McGrath III wrote: Yeah, R, that's why it's a nightmare! I don't wanna be Rambo or Carrot Top. So why do they keep coming into my nightmares Just Askin! Speaking as a person with red hair (that's going grey quite quickly) . . . the answer to the second on i

Re: How to send a number as a number or How to rule an LED

Yeah, R, that's why it's a nightmare! I don't wanna be Rambo or Carrot Top. So why do they keep coming into my nightmares Just Askin! -- Tom McGrath III http://lazyriver.on-rev.com 3mcgr...@comcast.net On Feb 5, 2011, at 12:37 PM, Richmond wrote: > Um? One wonders how a Sylvester Stallone

Re: Live LiveCode Code Event #9

This is your friendly reminder-service, that the event will start within the hour on marks stream and on chatrev: View here: http://livecode.tv/mark/ Talk here: http://bjoernke.com/chatrev/ On 3 Feb 2011, at 14:45, Björnke von Gierke wrote: > Hi persons that are on the edge of your seats > > T

Re: Hex values for Crayola colors

Cool link! Thanks for sharing that. :) That brings a question to mind though... what is the simple way of converting RGB codes to their hex equivalents? I think I used to know that, but am likely having a senior moment. ;-) Best regards, David C. ___ u

Barely competition

"Baycard" was recently brought to my attention: No scripting language, but it's in the MacApp Store now. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _

Re: How to send a number as a number or How to rule an LED

On 02/05/2011 06:32 PM, Thomas McGrath III wrote: Mark, I know what you mean. I spend so much time, sometimes, tracking down a problem in my code that I just want to join the army and charge up a hill screaming "Kill, kill, kill" until someone jumps up and shoots me in the shoulder and the for

Re: How to send a number as a number or How to rule an LED

Claudi, What is your atoi() code like? Why tDataStr[8] ? is that the number of chars you can read in? can that be more? What if we want to send "<13-125>" can we parse that to separate out the 13 for Pin 13 and the 125 for brightness? What about "<13-1-125>" and "<13-0-1>" for pin 13 output 12

Re: How to send a number as a number or How to rule an LED

Mark, I know what you mean. I spend so much time, sometimes, tracking down a problem in my code that I just want to join the army and charge up a hill screaming "Kill, kill, kill" until someone jumps up and shoots me in the shoulder and the force of the shot spins me around and now I'm falling

Re: How to send a number as a number or How to rule an LED

Hi tom, I am working with the same. What I undersrtand and have found on forums etc you need to use atoi() to convert from type char to int. You send out 3 chars when sending for instance, 125. The arduino seial.read routine will fetch 3 chars (125) I use a startChar 1 or more data chars and then

Re: Hex values for Crayola colors

Thanks Mark, I think I'll add this to the Point and See colour picker, great find. - Andy Piddock My software never has bugs. It just develops random features. PointandSee is a FREE simple but full featured under cursor colour picker / finder. http://www.pointandsee.co.uk - made with LiveC