Hello August!
On 26.04.19 at 20:25, August Abolins wrote to Martin Foster:
MF>>>> I thought I'd box clever<g> and convert one of my existing message
MF>>>> areas from the proprietary AMF format to JAM.
MF>>>> Everything appeared fine until I exited and restarted APoint..
AA> I believe you were tackling a JAM format issue with Apoint back in 2003:
AA> ----[begin]----
AA> From: Martin Foster
AA> To: Russell Tiedt
AA> Date: 2003-01-14 09:12:32
AA> Subject: APoint
AA> Yes it does BUT I'm sorry to say that it's flawed. APoint will handle a
AA> JAM message base that APoint itself has created but if you hook up APoint
AA> to an already existing JAM message base created by another program, it
AA> will read the message base just fine but it will not write to it
AA> correctly. This has been a long-standing problem and I hope the author(s)
AA> will fix it for the next release.
AA> -+- Msged/BeOS 6.0.2
AA> + Origin: Bitz-Box (2:250/501.2)
AA> ----[end]----
AA> Was Apoint at 1.25 back then?
AA> ../|ug
AA> -+- OpenXP 5.0.38
AA> + Origin: From somewhere in Hastings County, Ontario (2:221/1.58)
On 03.05.19 at 17:53, August Abolins wrote to Martin Foster:
AA>>> So.. "Apoint JAM base = Proprietary + Fails to display Quantity of
AA>>> messages in Area list.
MF>> Errrrrrrm, no, APoint AMF message base = proprietary.
AA> But way back in the day, you wrote that Apoint does not work with pre-
AA> exisiting JAM message bases.
Yes, that's correct.
AA> Which led you to believe that Apoint utilized a proprietary
AA> version of its own JAM.
Don't think it did.
AA> Will WinPoint work with the standard JAM produced from another source, or
AA> will it barf?
WinPoint doesn't support JAM at all.
MF>> ...but the messages are still there when you go into
MF>> the message list.
AA> But who will want to embrace Apoint if it behaves like that?
Probably nobody.
AA> To me, that's "broken".
You say "broken", I say "cosmetic" :-)
Regards,
Martin
--- OpenXP 5.0.38
* Origin: Bitz-Box - Bradford - UK (2:240/2188.31)
|
Point usage discussion and syste... 
