Page: 0 ... 5 ... 10 ... 15 ... 20 ... 25 ... 30 ... 35 ... 40 ... 45 50 51 52 53 54 55 56
Date: 22/3/2006
Lgi now builds and runs on cygwin with GCC. I tested this by building the IDE with Visual C++ and then loading the XML project files that LgiIde uses, and building it again with gcc. After a while I got it to a point where the GCC version doesn't crash. It's not fully tested but at least something is working. Most of the issues were with using mis-matched DLL's, ie some that were compiled with VC and some were GCC. This obviously "Does Not Work(TM)".

A release of Lgi will be out shortly.
(0) Comments | Add Comment

Date: 18/3/2006
It builds! After several months of inactivity, I used Kubuntu under Vmware to get Lgi + Scribe building again, mostly cause I need to valgrind the new Btree/Bayesian filtering code but nice to have it ready for the first v1.89 release "any time now".
(0) Comments | Add Comment

2 Steps Forward - 1 Step Back
Date: 17/3/2006
Well I got Scribe's bayesian rebuild memory footprint down to a mere 300mb instead of a whole 1gb this morning. Which is kinda on par to what it used to do. Still I think that is excessive and I'm going to play around with it some more when time permits. However it's no longer a big (pun intented) enough issue to prevent a v1.89 release. Just one little crash in the Btree code to sort out ;). I'm a little disappointed with how much I've got done in the months since v1.88 final but I guess all of you that emailed me questions and support issues are glad that I answered your mail, fixed your issues or at least had a look into whatever it was that was vexing you, right?

Notable blips on the support radar are non-functioning autozip plugin (partial fix is to more the DLL's into the Scribe.exe folder), more GPG relative path issues (ongoing) and the usual mix of "can't connect" type problems.

Not to mention in the meantime I've updated quite a few of my other apps (i.Mage and i.File come to mind) to fix annoying bugs (i.Ftp is next). And looked after my family and rested up a bit. And speaking of rest, tonight I'm taking off so that I can catch up with some of my friends and watch my new DVD:

Update: Well I was getting some screwy numbers out of the bayesian filter... and I tracked it back to case sensitivity in the Btree keys. E.g. adding 'This' to the Btree would delete the value stored for 'this'. So I made all the keys case-insensitive which suits my needs by changing all the calls to 'strcmp' to 'stricmp'. Now the filter is working as well as the old text file way of doing it. I still have that nagging crash I saw this morning and a memory overwrite this afternoon that worry me (probably the same thing). So I'll get it building on Linux and valgrind the sucker. That should be a few hours work but it'll show up the bug for sure. Then we're ready to roll with v1.89-test1.
(0) Comments | Add Comment

Html Editor
Date: 16/3/2006
Work continues slowly on the HTML editor built on top of the HTML viewer control that ships with Scribe. It now has a toolbar:

Recent changes are:
  • Added backspace/delete handler.
  • Delete with simple selection now works.
  • Fixed blocks of text overlapping by 1px.
  • Fixed drawing of selections.
  • Added deselecting with the cursor keys.
  • Added painting of the cursor while selection active.
  • Added a non-functional (but pretty) toolbar. Functions will follow.
  • Fixed cursor taking time to catch up with editing.

Sure it's no InnovaStudio but I own all the code and it's cross platform and small. So there.
(4) Comments | Add Comment

GnuPG Security Flaw
Date: 10/3/2006
For those of you that use the gpg plugin for Scribe, there is a security flaw in GnuPG, so if you use gpg you should update your install to the current version immediately.
(0) Comments | Add Comment

Windows Is Fun
Date: 9/3/2006
Yesterday my PC started the same old trick of ignoring the pre-set video resolution/refresh that I had asked for and set it to some seemingly random res... well seemingly random until I worked out what machine uses that res. My Res util reported that windows was running in 1440x900x32bit @ 75hz. Which is of course what this machine runs at... not the 1280x1024x32bit @ 75hz that MY machine SHOULD be running at (what IS that, operating system envy?). Like I can understand XP choosing a refresh mode out of thin air, but changing to frigging resolution on me? Damn thats low. Of course the LCD just thumbed it's nose at the whole thing and I had to hard power cycle XP to get something running again.

Update: I'm having some luck with a util called Reforce to force refresh rates to what I want regardless of whether the monitor is plugged in or not. *fingers crossed*
(0) Comments | Add Comment