At least in the last week or so I found the coding motivation that I seemed to have misplaced. I did some hacking on Paladin and was amazed at how easily a couple of features came together. I *finally* managed to make drag-and-drop group reordering work correctly. This has been a feature that I've been personally missing since drag and drop was implemented in the project window. There's even a visual regular expression tester that's been added to the Tools menu.
The feature that's holding things up is the Code Library. The concept? Encourage (and in my case, simplify) code reuse by creating modules of code that, once imported into a project, remain synchronized with the master copy. It's a little like source control, but on a more basic level. It seems simple on the surface, but it's turning out to be more of a challenge than I thought. I personally plan to use it a *lot*, so I'm waiting to get it right before the next release.
Nice to see you back up and running DarkWyrm, please continue with the lessons, they're very interesting :)
ReplyDeleteCheers,
That's good news, indeed!
ReplyDeleteSince you're back to play with Paladin... Paladin seems to be stuck on "Examining source files" whenever I change anything in Settings|Build. I'm also not sure the settings there have any influence...
This is version 1.1.b1.
Thanks!
I still plan on continuing the lessons. Expect to see another one later this week. :)
ReplyDeleteThanks for the bug report, Humdinger. I've noticed the same problem on occasion. I *think* it's related to the multithreaded build feature. Try enabling single-threaded builds, possibly trying to build again after restarting Paladin afterward. It may be a decent workaround until I can nail down the problem more precisely.
Enabling single-threaded build doesn't help. I changed the project setting to optmizing=more and even after restarting Paladin, I get a "Examining source files" when building.
ReplyDeleteThe build thread debugs as follows:
[Switching to team /HiQ-Data/apps/Paladin/Paladin (6004) thread build thread (6024)]
0xffff0114 in ?? ()
(gdb) bt
#0 0xffff0114 in ?? ()
#1 0x0051f70c in acquire_sem_etc () from /boot/system/lib/libroot.so
#2 0x0046502e in BLocker::AcquireLock () from /boot/system/lib/libbe.so
#3 0x004650c4 in BLocker::Lock () from /boot/system/lib/libbe.so
#4 0x0025f6e9 in ProjectBuilder::BuildThread ()
#5 0x0051fca0 in thread_entry () from /boot/system/lib/libroot.so
#6 0x700c1fec in ?? ()
Hmm, restarted Paladin again and now it works...
Anyway, no show-stopper.
Thanks
Humdinger