On Tue, 22 Aug 2000, Juergen Vigna wrote:
>
> > 3. Add "UndoAll" to the output of the appropriate states in all the
> >policies.
>
> I didn't really read what this UndoAll is (is there some documentation
> in the Policies file?), I think that I just need that after the first
> change the Re
> 3. Add "UndoAll" to the output of the appropriate states in all the
>policies.
I didn't really read what this UndoAll is (is there some documentation
in the Policies file?), I think that I just need that after the first
change the Restore button is activated and after pressing resotore, ok
On Mon, 21 Aug 2000, Juergen Vigna wrote:
>
> On 19-Aug-2000 Baruch Even wrote:
> > On Sat, 19 Aug 2000, Baruch Even wrote:
> >
> >> Whoever did the new FormDocument, I BLAME YOU!
> >
> > Sorry for this harsh language, I'm too tired to think anymore. I apologize
>
> You shouldn't be sorry it
On 19-Aug-2000 Baruch Even wrote:
> On Sat, 19 Aug 2000, Baruch Even wrote:
>
>> Whoever did the new FormDocument, I BLAME YOU!
>
> Sorry for this harsh language, I'm too tired to think anymore. I apologize
You shouldn't be sorry it was friday, wasn't it ;)
Anyway I've seen Allan fixed this a
Baruch Even wrote:
>
> On Sat, 19 Aug 2000, Baruch Even wrote:
>
> > Whoever did the new FormDocument, I BLAME YOU!
>
Sounds like a brown paper jug to me:) (See ChangeLog)
Garst
On Sat, 19 Aug 2000, Baruch Even wrote:
> Whoever did the new FormDocument, I BLAME YOU!
Sorry for this harsh language, I'm too tired to think anymore. I apologize
if (and even if not) someone got hurt by this. Wouldn't happen again in
the next 8 hours. I Promise! :-)
(I also claim that I'm sti
Whoever did the new FormDocument, I BLAME YOU!
I've been chasing the last hour or two (after being up all night) chasing
a bug that was supposedly in my code, after chasing it off with the unkind
help of ddd/gdb I found the culprit to be (supposedly, havent verified it
completely) in the function
