Loading ...
Sep
29
First of all, I’d like to think all of the well-wishers I’ve heard from recently. Comments, emails, and IMs have come in from many good people, some of which I had figured would never read this website.
On to other things…
Students and educators, be sure to check out our new Educational Sales program via the link on the left side of the page.
I’ve gotten reports that GraffitiSuite has problems in 2008R4. Although I’m unsure why, the problem happened on Leopard, and was solved by redownloading the currently available version.
Read on for GraffitiSuite and company stuff…
Next up, updates. I worked through the weekend on the next GraffitiSuite update. So far, it’s focused mainly on the StatusBar. I’ll go ahead and give you a teaser: Leopard Styles!
A few bug fixes are also hopefully going to make it into this release, and I plan to(at some point) reopen a bug reporting system.
As you may have noticed, I have two new links on the left-hand side. One of which, CyphersTech.com, is the new Envied Design.net parent company. So, at some undetermined point in the future, we’ll be switching a lot of stuff over to there. That’s also where a lot of the new pieces and parts of our infrastructure will show up. Envied Design.net isn’t going anywhere, and it will continue to house GraffitiSuite and any other REALbasic-oriented stuff we pump out.
The other, CraneTrax.com, does have a specific purpose but it’s still in the development stages. I’ll be telling everyone more about that later.
Meanwhile, check out the new little Support Widget on the left side of the page, thanks to Digsby.com. I can get those messages anywhere via their really cool Instant Messaging system.
5 Responses to “A few things…”
Leave a Reply
Says:
September 30th, 2008 at 6:33 pm
Well i don’t know if I add more confusion or information. The version of GraffitiSuite that bugged out on me had a timestamp dated August 22nd. The version that worked was timestamped as August 25th. Why there was a difference in 3 days is beyond me. But for whatever reason RB was throwing declare errors on loading project files using GSuite. In particular to GraffitiFadePanel. Checking the dates though. Both FadePanel’s were built and last saved 22nd. Only thing I can think of was maybe your IDE got bugged on a save.
I’ll pull the old one out of Time Machine and do a diff on the two and see what comes up. (diffing encrypted binary is fun!)
Who knows. I’ve got so many projects going on I might have spaced updating and was running a beta. Wouldn’t be the first time I have ever done that.
Says:
September 30th, 2008 at 7:34 pm
Ok diff is back and boy is it not what i expected.
3 files changed between the two versions GraffitiFadePanel.rbo, GraffitiPaintEngine.rbo, GraffitiRegistration.rbo.
the bugged version of GraffitiFadePanel.rbo had
B
Says:
September 30th, 2008 at 7:53 pm
That’s very strange. There were no really significant changes in the GraffitiPanel since before the last beta. It would have to be a bad save. Either way, the newest works, and I’m grateful for that.
Says:
September 30th, 2008 at 8:00 pm
Great. Ok maybe my computer just hates me. LOL
Nah there was characters got pasted in that i had filtered out but I obviously didn’t. Hense getting my comment clipped.
Ok what i found is that object had been completely replaced with a metadata file of some sorts. The bug was something that must have happened a while back and just now caught.
I’m chalking this one down to the joys of dealing with a RAD IDE is that sometimes the editor geeks out and does something retarded. It’s the price you pay for not managing all your project files by hand.
I’m isolating it to just being me bugged as it had very explicit data stored that was unique to my developing workstation.
Although if it wasn’t just me I will say it is a bug in RB converting projects from a R3.1 format to a R4 on a Mac.
Either way there is no problem at all on GraffitiSuite’s end of things as far I can tell.
Says:
September 30th, 2008 at 9:16 pm
While I’m skeptical of my own work being to blame(and what developer isn’t), it may have been my fault. I am, sometimes, drawn to blame the development environment(which may be the case here), but I’m not positive. I wish we knew more about the root of the problem so I could possibly keep it from occurring in the future, but I won’t lose sleep over it since it’s fixed.
Thanks for all of your insight.