Independent web developer. Graphic designer, web designer, Frontier developer, Manila hoster, latest project: intranet build for Government Office of West Midlands (UK), committed blogger since 1999.
See more details on services and more personal background who and where.
email 'spam free' or phone on: inside UK: 0800 849 6413 or outside UK: +44 1952 271 671 or mobile (and txt): +44 7903 940 427
"Bug fix. Please update your tool by going to your Radio app Tools menu ==> backLogAllRSS == Refresh code..."
Bugs, this damn thing has been plaguing me for months, finally I track it down and <falls off chair> it's my own damn bug!
Apologies to those who've experienced this one. It was hard to track down, as it was occurring in the process macros calls. Which are hard to spot as they look like they're in the kernel, but if you press step in the debugger, on the kernel call in the processMacros script, you can press in and out of all the macros that occur in the page you're debugging at system.verbs.builtins.html.buildObject. I remembered you could do that before the macro was kernalised but didn't realise that you could continue to debug, even there.
|See where you catch the processMacros call in buildObject? Then press step to the hand in processMacros where I thought I'd lose it in the kernal.|
|But, by pressing in here, you go to the first macro in your page
(including the template, this is in the final run through processMacros in the pagefilter part of building a
page, just after the page has been added to the template.)|
My bug was in the radio.macros.weblogEditBox where at, the very bottom, it, unexpectedly, then calls radio.macros.weblogRecentPosts, even though it's in my template as a stand alone macro.
Nice. Even if it took me months to discover. And then that it was my own bug!
They can track you through your cell phone, so why not your DVD player? Microchips planted in electronics, computers and other household objects will alert the cops to any sudden change in location, which might suggest theft.