John,

it seem I stuffed up, after last udate scripts n longer run.... What did I
forget?


Voytek Eymont
___
Sent with SnapperMail
www.snappermail.com

{LFREGEXP::
/&runtimeInit[]
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
/p10/p10
/xEpro f
/&script$[@@LFR0@@]}
{LFR0::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@ @@]}
{LFR1::
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
/p10
/&script$[@@LFR2@@]}
{LFR2::
/&tap i[080,080]
/&script$[@@LFR3@@]}
{LFR3:: ß
/xEpro f
/&script$[@@LFR4@@]}
{LFR4:: A
/&script$[@@LFR5@@]}
{LFR5:: d
/&script$[@@LFR6@@] }
{LFR6::
/xEpro f
/xEpro T/xEpro W/xEpro R
ßß*
/&script$[@@LFR7@@]}
{LFR7::
/&tap i[080,080]
/&script$[@@LFR8@@]}
{LFR8::
/p10
/xEpro f
/&script$[@@LFR9@@]}
{LFR9::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@ @@]}
{LFR10::A
/&script$[@@LFR11@@]}
{LFR11:: d}


{ColonDelete::
/&runtimeInit[]
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
:
/xEpro f
/&script$[@@CD2@@]}
{CD2::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@ @@]}
{CD3::
/0x1C
/xEpro s1
/&control[@@bWord@@]
/&script$[@@CD3A@@]}
{CD3A::
/&script$[@@CD3AA@@]}
{CD3AA::
/e#
/&ifScript@[$$!=0,@@CD3C@@]
/&ifScript@[$$==0,@@CD3B@@]}
{CD3B::
/0x1D/0x1D
/&script$[@@CD3D@@]}
{CD3C::
/0x1D/0x1D
/0x08 ;
/&script$[@@ColonDelete@@]}
{CD3D::
/0x1C
/xEpro j 1
/&control[@@bLine@@]
/&script$[@@CD4@@]}
{CD4::
/&script$[@@CD5@@]}
{CD5::
/e@
/&ifScript@[$$==58,@@CD7@@]
/&ifScript@[$$!=58,@@CD6@@]}
{CD6::
/0x1D
/0x08
/&script$[@@CD5@@]}
{CD7::
/0x1D
/0x08
/&script$[@@ColonDelete@@]}


{LFdelete::
/&runtimeInit[]
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
/p10/p10
/xEpro f
/&script$[@@LFd0@@]}
{LFd0::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@ @@]}
{LFd1::
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
/p10/p10
/&script$[@@LFd2@@]}
{LFd2::
/&tap i[080,080]
/&script$[@@LFd3@@]}
{LFd3::
/p10
/xEpro f
/&script$[@@LFd4@@]}
{LFd4:: A
/&script$[@@LFd5@@]}
{LFd5:: d}


{SPdelete::
/&runtimeInit[]
/xEpro f
/xEpro T/xEpro W/xEpro R
/xs/xs
*
/&script$[@@SPd2@@]}
{SPd2::
/&tap i[080,080]
/&script$[@@SPd3@@]}
{SPd3::
/p32
/xEpro f
/&script$[@@SPd4@@]}
{SPd4::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@ @@]}
{SPd5::A
/&script$[@@SPd6@@]}
{SPd6:: d}


...

Quoting Voytek Eymont <voytek@...>:

> John,
>
> it seem I stuffed up, after last udate scripts n longer run.... What
> did I forget?

Well, that's my fault, I wasn't specific enough, by trying to cover
all four pScripts in one instruction.  Here is what I posted -

>> 1) In all four pScripts there are two lines,
>>
>> /&ifAbort@[$&==0]
>> /&ifScript@[$&>0,@@ @@]}
>>
>> In the second line, change $&>0  to $&!=0
>>
>> so that it reads    /&ifScript@[$&!=0,@@ @@]}

Since I was referring to all four, I left the specific pScript
identifiers out, thinking you would put them in, in the spaces between
the "@@  @@" in
/&ifScript@[$&>0,@@ @@]}.  I should have pointed that out to you.  So,
to be specific -

in {LFREGEXP::     it should read      /&ifScript@[$&!=0,@@LFR1@@]}

in {ColonDelete::    it should read      /&ifScript@[$&!=0,@@CD3@@]}

in {LFdelete::     it should read      /&ifScript@[$&!=0,@@LFd1@@]}

in {SPdelete::     it should read      /&ifScript@[$&!=0,@@SPd5@@]}

That should do it.  Let me know.

Also, do you have pToolSet, and if you do is it the same version
number as your peditPro?  And, if you have pToolSet do you know how to
use pScriptButtons?
And, if you were to have a pScript to move memo to DateBk6 Note, what
would be your sequence of actions?

~ John

<quote who="John Markley">

> Also, do you have pToolSet, and if you do is it the same version
> number as your peditPro?

no:
peditPro 8.15
pToolSet 8.14

(how do you lookup ptoolset version, I've used Palm's 'Info' to look it up ?)

not sure there is 8.15 pToolSet
http://home.roadrunner.com/~nevai/palm/versions.html says 8.14

> And, if you have pToolSet do you know how to use
> pScriptButtons?

ahem, you gave me a tutorial on it, though, I'm still struggling with it,
and, can't say I've mastered it

> And, if you were to have a pScript to move memo to DateBk6
> Note, what
> would be your sequence of actions?

at a guess, select all/copy, command stroke to get pToolSet and use a tool
from pop up menu ?




--
Voytek

is there a way to have like an image or two associated with an image tool,
say, Resco, to be able to open an image from a note/address book ?

either a link or DA...?

something like MapDA, but, rather than doing a gmap lookup, open an
existing image in a viewer ?

say I get an address, I do a map lookup, I'd like to keep that map(s) for
next time I need them (and I might not have connectivity at that point)

so, I'd like to save the image in a note to appointment, or, address book
note, then, if needed, click on the link to invoke image viewer with that
image, or, select image file name and DA it ?

(to save the need to invoke an image viewer then look for desired file)


--
Voytek

<quote who="Voytek Eymont">
> is there a way to have like an image or two associated with an image
> tool, say, Resco, to be able to open an image from a note/address book ?
>

John,

I've just found your earlier advice on this:
I guess I need to check pslink

==============
> (is that what pslink is for ?)

    Yes. PsLink will definitely take you from DateBk to RescoViewer.  It
may or may not take you to the specific image, you'll have to
experiment.  When installed, PsLink appears in the Palm Prefs screen at
the bottom.  In PsLink main screen, open the "More" button and choose
one of the 5 "More Link" screens and select RescoViewer in the
Application list.  You may have to experiment with the Database, but
usually "Default" will do it.  I've changed the start and end default
brackets to vertical bars, "|", for my own purposes and don't recall
what the original default was, maybe "{" and "}".  Whatever the start
and end tag brackets in your PsLink are, you need to add a unique
identifier for your RescoViewer link, such as perhaps "r", so your
start tag would be { and the End tag would be }r.  Then you would put
{xxxx}r in you DateBk appt, where "xxxx" is the name of your image.
When you double tap inside {xxxx}r it will jump to RescoViewer, and
*maybe* to the image.  As I just recently found out, *do not* check the
box on the main PsLink screen that says "Action with single tap" unless
you don't mind, if you try to edit a date text of the form mm/yy/dd by
putting the cursor in it, instantly jumping to that date in DateBk --
very annoying.  Leave it unchecked and use a double tap to activate
your PsLink link.




--
Voytek

<quote who="John Markley">

> Since I was referring to all four, I left the specific pScript
> identifiers out, thinking you would put them in, in the spaces between the
> "@@  @@" in
> /&ifScript@[$&>0,@@ @@]}.  I should have pointed that out to you.  So,
> to be specific -
>
> in {LFREGEXP::     it should read      /&ifScript@[$&!=0,@@LFR1@@]}


This script has two instances,

... does the @@label refer to the label immediately AFTER...?


2nd instance needs '10', yes ?



{LFR9::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@LFR10@@]}
{LFR10::A

(seems to work, I'll test more later today)

--
Voytek

after several passes of LFdelete, I got 'no more' message, followed bu
'Ad' trailing behind very last text on very last line.

that's the only 'Ad' I got

I'll do more passes later today

overall, we're looking really good

it seems that Colondelete followed by several (2 or 3) LFDelete does
everything I need

but, I'll do more passes later

thanks again


--
Voytek

Quoting Voytek Eymont <voytek@...>:

>> in {LFREGEXP::     it should read      /&ifScript@[$&!=0,@@LFR1@@]}

> This script has two instances,
>
> ... does the @@label refer to the label immediately AFTER...?
>
> 2nd instance needs '10', yes ?
>
>
> {LFR9::
> /&ifAbort@[$&==0]
> /&ifScript@[$&!=0,@@LFR10@@]}
> {LFR10::A

Ah, sorry, yes, it should be @@LFR10@@ in this case.  However, in
general the pScript name within the @@ @@  in the "/&ifScript"
pFunction does not refer to any particular location in the chain, it
refers to the specific pScript name no matter where in the pScriptPad
it is.  These long complex items to do specific tasks that I've been
sending you are *chains* of pScripts.  That is, you don't have 4
pScripts from me, you have a couple dozen (haven't counted) - but,
each individual pScript (except for the last one in each chain) has as
its last command to activate another pScript. So, LFR9 says, if there
is no text selection STOP (&ifAbort), but if there is a text
selection, i.e. a find for the search, then go on and run the pScript
named {LFR10.  *But*, {LFR10 could be anywhere in your pad, not
necessarily right after {LFR9.  Paul's program searches the pScriptPad
for the specific name each time, which is why you cannot have more
than one pScript with the same name.

     ~ John

Quoting Voytek Eymont <voytek@...>:

>
> <quote who="Voytek Eymont">
>> is there a way to have like an image or two associated with an image
>> tool, say, Resco, to be able to open an image from a note/address book ?
>>
>
> John,
>
> I've just found your earlier advice on this:
> I guess I need to check pslink


That's the only way I know.  Perhaps someone else here has another way(s).

    ~ John

Quoting Voytek Eymont <voytek@...>:

>
> <quote who="John Markley">
>
>> Also, do you have pToolSet, and if you do is it the same version
>> number as your peditPro?
>
> no:
> peditPro 8.15
> pToolSet 8.14

    There is no peditPro v. 8.15.  The current version is 8.14, as is pToolSet.
Open pedit, do menu/options/about pedit.  It should say 8.14.
>
> (how do you lookup ptoolset version, I've used Palm's 'Info' to look it up ?)

Open pMasterTool (that is the pToolSet "list" via command stroke, and
with the list open do menu/pMT2/Version info.  That too should say 8.14.


>> And, if you have pToolSet do you know how to use
>> pScriptButtons?
>
> ahem, you gave me a tutorial on it, though, I'm still struggling with it,
> and, can't say I've mastered it
>

OK, you need to learn that as it will simplify using your pScripts.
Modified tutorial to address pScriptButtons at the end of this post.


>> And, if you were to have a pScript to move memo to DateBk6
>> Note, what
>> would be your sequence of actions?
>
> at a guess, select all/copy, command stroke to get pToolSet and use a tool
> from pop up menu ?

OK.  When you have pScriptButtons working we can do a pScript that
will simplify memo to note for you.

PScriptButtons -

    This is well explained by Paul in the pToolSet Manual, and I
suggest that you read that at some point, but here is a quick how to.

1)  Open your pScriptPad, and at the very top write

custBtnPageTotal=2

exactly like that, no spaces.  That will give you two pages of
pScriptButtons, 20 total, 10 per page.  You can increase the number as
you like, up to 999.

2)  On the line of the pScriptPad just above your first pScript or
pScript chain put

custBtn.001.1

so if for example your first item is the chain that starts with
{ColonDelete::, you would have in your pad

custBtn.001.1
{ColonDelete::
/&runtimeInit[]
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
:
/xEpro f
/&script$[@@CD2@@]}
{CD2::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@ @@]}  and so forth to the end of the chain.

Then, on the line of the pad just above the first script in your next
chain, whatever that is ( {LFdelet:: , {SPdelete::, whatever), put

custBtn.001.2

Then above the next pScript chain put

custBtn.001.3,

   and so forth, until you have a custBtn.xxx.x label for each of your
pScripts/chains.  I think you have less than ten.  If you get to
custBtn001.0, the tenth button in the .001.x series, then you would go
to custBtn.002.1, etc.

3) Now, close the pScriptPad, open pMasterTool (the command slash
pToolSet), and tap pScriptButtons.  Voila.  If you tap the item with
the name of the script that you want, it will run.  You will need this
to run the upcoming memo-to-DateBk pScript.  *WARNING* - if you use
pScriptButtons to run one of your pedit memo pScripts and you are not
in pedit at the time, it may print some nonsense in whatever app you
are in.  So to begin with you should only try this with a pedit memo
open in which case it will do the same thing as you have been doing so
far.  If you like the buttons I can easily slightly modify your pedit
memo scripts so they will only run if you have pedit open.  My reason
for bothering you with this seeming complication is that it opens the
power to use pScripts while in any app for you, and gives you a
one-stop-shopping index to activate any of your scripts without having
to remember their names.  Furthermore, if you like it we can program
your TX/T3 to open the buttons with a screen tap or button press
without having to go through the command pToolSet list step.

Quoting Voytek Eymont <voytek@...>:

> after several passes of LFdelete, I got 'no more' message, followed bu
> 'Ad' trailing behind very last text on very last line.
>
> that's the only 'Ad' I got
>
> I'll do more passes later today
>
> overall, we're looking really good
>
> it seems that Colondelete followed by several (2 or 3) LFDelete does
> everything I need
>
> but, I'll do more passes later

Ah, OK, I see why, but I'm not sure if I can fix it.  Meanwhile run
LFREGEXP the same way, multiple passes, and see if that does what you
want.

    ~ John

Quoting John Markley <jmmjr@...>:

> Quoting Voytek Eymont <voytek@...>:
>
>> after several passes of LFdelete, I got 'no more' message, followed bu
>> 'Ad' trailing behind very last text on very last line.
>>
>> that's the only 'Ad' I got
>
> Ah, OK, I see why, but I'm not sure if I can fix it.  Meanwhile run
> LFREGEXP the same way, multiple passes, and see if that does what you
> want.

OK, I think this is the fix.  Each time you run LFdelete, when it is
done there is a blue (or some color) selection showing in a blank
space.  Tap the screen to turn that into a flashing cursor before you
run LFdelete again, and I bet you don't get the 'Ad' any more, no
mater how many passes.  Let me know --

    ~ John

Quoting John Markley <jmmjr@...>:

>>> And, if you were to have a pScript to move memo to DateBk6
>>> Note, what
>>> would be your sequence of actions?
>>
>> at a guess, select all/copy, command stroke to get pToolSet and use a tool
>> from pop up menu ?
>
> OK.  When you have pScriptButtons working we can do a pScript that
> will simplify memo to note for you.

Here are two pScripts (chains) each of which will transfer your memo
to a DateBk note, in different ways.  You don't need to bother with
pScriptButtons for these if you don't want to, you can run them from
pedit the same way as you've been doing for the other pScripts.

{pDateMemoNote::
/xc Z
/xc C
/0x1C
/xEpmt g  MemoNote
/&control[@@note@@]
/&script$[@@pDM1@@]}
{pDM1::
/xc P
/&script$[@@pDM2@@]}
{pDM2::
/xEpet o}

This first one, {pDateMemoNote, will select all the text in your memo,
copy it, open pDateTool, writes the title "MemoNote" as the DateBk
item, pastes your memo into the note, and stops so you can select a
date and time and then manually tap "Add New Item".  You can then jump
to DateBk using the pDateTool menu item "Go To DateBook" (or just open
DateBk with your DateBk button).  However, that will take you to
today's date.  There is no way to jump directly to the entry you just
made if it is on a different date than today.  I put the item line
"MemoNote" in because pDateTool will not do the transfer to DateBk if
the "add your DateBook item here" line is blank.

*******

{MemoToNote::
/xc Z
/xc C
/0x1C
/&script$[@@MTN1@@]}
{MTN1::
/&launch[@@DateBk6@@]
/xc N
/&control[@@No@@]
/&script$[@@MTN2@@]}
{MTN2::
/&script$[@@MTN3@@]}
{MTN3::
/xc A
/xc P}

The second one, {MemoToNote, will copy the memo, open DateBk, open a
new DateBk untimed item on today's date, open a new note and paste
your memo, and stop.  You will have to manually set the date and time,
and whatever item name you want.

What I cannot do is make it so you can start in DateBk in a
pre-existing item or note, jump to the correct memo, copy, and return
to the correct DateBk item all automatically, as pedit and DateBk do
not have this capability.

See if you like either one, and if there are any changes you'd like.

    ~ John

Quoting John Markley <jmmjr@...>:

> Here are two pScripts (chains) each of which will transfer your memo
> to a DateBk note, in different ways. ...... ((SNIP))
> You can then jump
> to DateBk using the pDateTool menu item "Go To DateBook" (or just open
> DateBk with your DateBk button).  However, that will take you to
> today's date.  There is no way to jump directly to the entry you just
> made if it is on a different date than today.

oops, nope, wrong -   you *can* jump directly to the entry you just
made.  While still in pDateTool, after the little message "added
DateBook item" confirms the transfer, do menu/Go To Last Item, and it
will take you directly to your DateBk entry of whatever the date you
chose for it.

    ~ John

Quoting John Markley <jmmjr@...>:
>
> OK, I think this is the fix.  Each time you run LFdelete, when it is
> done there is a blue (or some color) selection showing in a blank
> space.  Tap the screen to turn that into a flashing cursor before you
> run LFdelete again, and I bet you don't get the 'Ad' any more, no
> mater how many passes.

Here is a better fix, a little addition to the pScript that will do
automatically what I suggested doing with a tap, above. At the start
of LFdelete, insert

/0x1C   after  /&runtimeInit[]    and  before  /xEpro f, so that it now reads

{LFdelete::
/&runtimeInit[]
/0x1C
/xEpro f
/xEpro T ......  etc,etc.

That will do it.

    ~John

>is there a way to have like an image or two associated with an image tool,

I am a PsLink and WikiZ user. WikiZ for standar built-in databases (Memo,
Contacts, Calendar
and Todos) is faster than PsLink.

Note that Note Pad might be useful for very simple drawings and PsLink can be
configered for it.


Going back to the previous appl:
PsLink allows you to configure two of the palm hard buttons for backward
and forward functionality but it is not very reliable.
pToolSet "open prev app" special action might be a good *non specific*
second option for this. Most of the programs will jump directly to the
specific previous document in that app.


I have one of the taps configured for this.

pToolSet prefs----> Taps-->
You might choose any of them.


Regrads,

Jose

<quote who="John Markley">

> Here are two pScripts (chains) each of which will transfer your memo
> to a DateBk note, in different ways.  You don't need to bother with
> pScriptButtons for these if you don't want to, you can run them from pedit
> the same way as you've been doing for the other pScripts.
>
> {pDateMemoNote::
> /xc Z
> /xc C
> /0x1C
> /xEpmt g  MemoNote
> /&control[@@note@@]
> /&script$[@@pDM1@@]}
> {pDM1::
> /xc P
> /&script$[@@pDM2@@]}
> {pDM2::
> /xEpet o}

John,

I get '/gMemoNote' inserted on the 1st line of the memo....the note is
copied to itself....  and not much else that I can see....

what did I miss ?


--
Voytek

<quote who="John Markley">

> There is no peditPro v. 8.15.  The current version is 8.14, as is
> pToolSet. Open pedit, do menu/options/about pedit.  It should say 8.14.

I must've a pre-rel version: 8.15 April 5th 09

but, it's time-crippled, it expires 20/7/2068....


>> (how do you lookup ptoolset version, I've used Palm's 'Info' to look it
>> up ?)
>
> Open pMasterTool (that is the pToolSet "list" via command stroke, and
> with the list open do menu/pMT2/Version info.  That too should say 8.14.

oops, I forgot there was a menu beyond the popup list...

8.14 feb 26 09


--
Voytek

Hi Guys:

I couldn't find a single meaningful review (based on actual usage) of an
extended battery for the Centro (or the 755p) on the net.

I can tell you that I purchased this Seidio extended battery (huge and
expensive) for both the Centro and the 755p and in each case they worked
great for about a month and then they stopped holding the charge. I did the
recommended preconditioning in both cases.

I even have a feeling that Palm may have built into the OS protection against
third party batteries. Could this be true?

Do you have any recommendations based on extended usage of any of the
extended batteries?

Let me add that Centro + Sprint + Central Ohio = winning formula.  No
comparison between the 755p and the Centro when it comes to their qualities
as cell-phones. I am even thinking of canceling my land-line. The Centro is
my first ever cell-phone that actually is usable as a phone (I was always a
Sprint customer).

All=my=best, Paul

Quoting Voytek Eymont <voytek@...>:

>
> <quote who="John Markley">
>
>> Here are two pScripts (chains) each of which will transfer your memo
>> to a DateBk note, in different ways.  You don't need to bother with
>> pScriptButtons for these if you don't want to, you can run them from pedit
>> the same way as you've been doing for the other pScripts.
>>
>> {pDateMemoNote::
>> /xc Z
>> /xc C
>> /0x1C
>> /xEpmt g  MemoNote
>> /&control[@@note@@]
>> /&script$[@@pDM1@@]}
>> {pDM1::
>> /xc P
>> /&script$[@@pDM2@@]}
>> {pDM2::
>> /xEpet o}
>
> John,
>
> I get '/gMemoNote' inserted on the 1st line of the memo....the note is
> copied to itself....  and not much else that I can see....
>
> what did I miss ?

That most likely means either that you do not have pToolSet turned on,
or that g is not the designator letter for pDateTool in your setup.
If your pToolSet is on, you will see the little p-home icon in the
command bar with command slash, and you will get the pMasterTool list
of pToolSet items when you tap it.  If it is off (no icon, no list),
use the little app "pToolOn" in your launcher to turn it on.  If/when
it is on, then look on the list and see what the letter or number is
that is to the left of pDateTool.  I expected it to be g:pDateTool,
resulting in the g in "/xEpmt g  MemoNote".  If it is a different
letter or number on your list, put the correct item in place of the g
in the script and it will work.  I suspect I know what happened, and
if so, you will find it is G, not g.
If neither of these is the case, let me know asap.

        ~ John

Quoting Voytek Eymont <voytek@...>:

>
> <quote who="John Markley">
>
>> There is no peditPro v. 8.15.  The current version is 8.14, as is
>> pToolSet. Open pedit, do menu/options/about pedit.  It should say 8.14.
>
> I must've a pre-rel version: 8.15 April 5th 09
>
> but, it's time-crippled, it expires 20/7/2068....

Well, you are correct.  I just went to Paul's website and downloaded
the current peditPro, and it is indeeed 8.15 (the 2068 expiration is
standard ala Paul, and does not designate a pre-release).

So now I'm wondering, how did I miss this, particularly since usually
when Paul releases a new pedit version he also does a matching
pToolSet version and sends that to registered users.  And, the website
says 8.14 is current for both. ??
Maybe Paul will comment...??

      ~ John

<quote who="fjmancho">
>> is there a way to have like an image or two associated with an image
>> tool,
>
> I am a PsLink and WikiZ user. WikiZ for standar built-in databases (Memo,
> Contacts, Calendar
> and Todos) is faster than PsLink.

John, Jose,

thanks

what the correct file path syntax if i have image.gif in the root of the
sd media ?


??? /image.gif



--
Voytek

<quote who="John Markley">

> That most likely means either that you do not have pToolSet turned on,
> or that g is not the designator letter for pDateTool in your setup. If your
> pToolSet is on, you will see the little p-home icon in the command bar

thanks, John

yes, it's ON

> with command slash, and you will get the pMasterTool list of pToolSet
> items when you tap it.  If it is off (no icon, no list), use the little

yes, vertical list in the centre

> app "pToolOn" in your launcher to turn it on.  If/when it is on, then look
> on the list and see what the letter or number is that is to the left of
> pDateTool.  I expected it to be g:pDateTool, resulting in the g in "/xEpmt

starts with:
1:pEditTool
...
7:pDateTool

tried '7' in the script, get

'/7MemoNotestuff'


> g  MemoNote".  If it is a different letter or number on your list, put the
> correct item in place of the g in the script and it will work.  I suspect
> I know what happened, and
> if so, you will find it is G, not g. If neither of these is the case, let
> me know asap.

apart from this, the scripts are behaving wonderfully!!

on a related matter, if I invoke pDateTool manully from pop up of from an
icon, Palm does a Phoenix and burns down, so it seems I have a problem
with some part of pToolSet

also: I'm running scripts against a different data sets, works well, though:

how can we remove single leading blank space?

if there are leading blank spaces, SPd get rid down to a single leading
space.

if I get tabs (visibilites to '>>', what the best way of getting rid of
them ? replace with space ? then SPd



--
Voytek

Quoting Voytek Eymont <voytek@...>:
> starts with:
> 1:pEditTool
> ...
> 7:pDateTool
>
> tried '7' in the script, get
>
> '/7MemoNotestuff'

That definitely should not happen if that line of the pScript reads
/xEpmt 7 MemoNote

what should happen is that pDateTool opens and "MemeoNote" is printed
in the top line.  See below.

> on a related matter, if I invoke pDateTool manully from pop up of from an
> icon, Palm does a Phoenix and burns down, so it seems I have a problem
> with some part of pToolSet

By "does a Phoenix" I take it you mean a spontaneous soft reset.  That
definitely should not happen either.  Please do several things:

1) Look at your pMasterTool ESC and your pedit ESC characters.  If
they are both the same character, change one of them (use a character
you don't ordinarily type).  For PMT ESC, open the pToolSet module
list (that *is* pMasterTool), and do menu/pMT1/pToolSet Prefs. For
pedit ESC do pedit menu/Op/Preferences/General.
In both of these make sure the box to use ESC is checked "on" (if
pMasterTool ESC is not on that would cause the '/7MemoNotestuff'
problem).

2) Test other pToolSet modules.  If others also generate crashes,
completely remove all the pToolSet modules and reinstall all of them
fresh.  To do this, open the app called pToolZapper in your app
launcher, tap "check all", select "no" in the "zap assoc prefs" line,
and tap "Done".  That will remove all of pToolSet.  Then do a hotsync
install of *all* the .prc in your pToolSet 8.14 folder.  Do not use
the sub-folder "00pToolButtons".  If when you test the pToolSet
modules only pDateTool misbehaves, remove it with pToolZapper and
replace.
3) If (1) and (2) don't fix it, post a separate query to Paul.  It is
rare to the point of zero for pToolSet itself to cause crashes. Such
instances have always been traceable to interference by other
background apps (hacks).


> also: I'm running scripts against a different data sets, works well, though:
>
> how can we remove single leading blank space?
>
> if there are leading blank spaces, SPd get rid down to a single leading
> space.
>
> if I get tabs (visibilites to '>>', what the best way of getting rid of
> them ? replace with space ? then SPd

More about this later.

> apart from this, the scripts are behaving wonderfully!!

Very good.  With regard to the "{MemoToNote:" pScript, which evidently
is working ok, it ends with your new DateBk memo open, rather than
closing the note and showing the entry in Day View by tapping the
"Done" button.  I did this because there was an exceedingly gnarly
problem getting the pScript to do that final "Done" button activation.
   I have now solved that with a rather cool little trick.  If you
would prefer to have the pScript end with the DayView entry rather
than the open note, replace your pScript with this one-

{MemoToNote::
/xc Z
/xc C
/0x1C
/&script$[@@MTN1@@]}
{MTN1::
/&launch[@@DateBk6@@]
/xc N
/&control[@@No@@]
/&script$[@@MTN2@@]}
{MTN2::
/&script$[@@MTN3@@]}
{MTN3::
/xc A
/xc P
/&varSet[$1,0]
/&script$[@@MTN4@@]}
{MTN4::
/&varAdd@[$1,1]
/&control[@@Done@@]
/&script$[@@MTN5@@]}
{MTN5::
/!/$f
/&ifAbort@[$$==1000]
/&ifAbort@[$1>=10]
/&script$[@@MTN4@@]}

         ~ John

Quoting John Markley <jmmjr@...>:

> Quoting Voytek Eymont <voytek@...>:

>> if I get tabs (visibilites to '>>', what the best way of getting rid of
>> them ? replace with space ? then SPd
>
> More about this later.

This will remove any string of one or more TABs and will replace the
entire string with one space -

{TABdelete::
/&runtimeInit[]
/xEpro f
/xEpro T/xEpro W/xEpro R
/p9
*
/&script$[@@TABd2@@]}
{TABd2::
/&tap i[080,080]
/&script$[@@TABd3@@]}
{TABd3::
/p32
/xEpro f
/&script$[@@TABd4@@]}
{TABd4::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@TABd5@@] }
{TABd5::A
/&script$[@@TABd6@@]}
{TABd6:: d}

      ~ John

Quoting John Markley <jmmjr@...>:

> Quoting Voytek Eymont <voytek@...>:

>> also: I'm running scripts against a different data sets, works well, though:
>>
>> how can we remove single leading blank space?
>>
>> if there are leading blank spaces, SPd get rid down to a single leading
>> space.

> More about this later.

Put this is your pScriptPad -

{LeadingSpaceDelete::
/&runtimeInit[]
/0x1C
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
/p10/p32
/xEpro f
/&script$[@@LSD0@@]}
{LSD0::
/&ifAbort@[$&==0]
/&ifScript@[$&!=0,@@LSD1@@]}
{LSD1::
/xEpro f
/xEpro T/xEpro W/xEpro R/xEpro r
/p10/p32
/&script$[@@LSD2@@]}
{LSD2::
/&tap i[080,080]
/&script$[@@LSD3@@]}
{LSD3::
/p10
/xEpro f
/&script$[@@LSD4@@]}
{LSD4::A
/&script$[@@LSD5@@]}
{LSD5:: d}

     and, change the last line of SPdelete to read -

{SPd6:: d
/&script$[@@LeadingSpaceDelete@@]}

Now when you run SPdelete it will also remove all leading spaces,
*except* if there is a leading space in the very first topmost line of
the memo.  That one you'll need to remove manually (I could make the
pScript do it but it adds a lot of complexity for one space at a known
location).


      ~ John

<quote who="John Markley">

> if so, you will find it is G, not g. If neither of these is the case, let
> me know asap.

John,

'escape' ('/')wasn't enabled in pTset, all good now

(though Palm still crashes, I'll look at reinstalling later today)

--
Voytek

Quoting Voytek Eymont <voytek@...>:
>
> John,
>
> 'escape' ('/')wasn't enabled in pTset, all good now
>
> (though Palm still crashes, I'll look at reinstalling later today)

(I just accidentally sent a non-response, please ignore, this is the
real thing).

OK, good.  However, I suggest that, since '/' is integral to the
syntax of pScripting, you replace it with something else, such as '\'.
   Not mandatory, but not a bad idea.

If you do a reinstall, first just zap and reinstall pDateTool and see
if that does it, unless you have found that the other pToolSet modules
also cause a crash.  And, before you do a total pToolSet zap and
reinstall, consider turning off any other background extensions
("hacks") you may have, one by one, and retest pDateTool, as most
likely it is a hack conflict of some sort.

      ~ John

<quote who="John Markley">

> This will remove any string of one or more TABs and will replace the
> entire string with one space -
>
> {TABdelete::


thanks, John.

as I now get 'stuff' from another source, the other source doesn't use ':'
but uses TABS to separate label from data;

I've duplicated TABdelete to TABreplace and, modeded '32' string to '58',
so, with the 'new stuff' I can run TABreplace followed by Colondelete,
that seems to work well


I'll test leading space deleter later, I've also kept the original
(renamed) SPdelete.

I'm testing screen scraping on a PC, emailing to the Palm, then processing
(which is most convenient compared trying to do web stuff on the tiny
screen), the resulting file is somewhat different (in terms of TABs and
stuff), also, testing with another source.

but the set of scripts you made make a pretty good 'web page sanitizer'



--
Voytek

Quoting Voytek Eymont <voytek@...>:

> thanks, John.

You are welcome.  I love doing this stuff.

> I'll test leading space deleter later, I've also kept the original
> (renamed) SPdelete.

You can run LeadingSpaceDelete by itself to test it if you wish.  If
you put the first few letters of "LeadingSpaceDelete" in the pScript
starter dialog it will run without having SPdelete run first.
*But*, just renaming the first pScript in the SPdelete chain, but not
all the linked pScripts in the chain ( SPd2, SPd3, etc) will not be
sufficient, because you will now have *two* SPd6 pScripts, one that
just ends, {SPd6::d}, and the other that links to LeadingSpaceDelete.
Again, each pScript in a chain is a complete pScript on its own, and
it doesn't matter what order they appear.  The command
"/&script$[@@xxx@@]}" says, as the final action of this pScript, go
find the pScript named xxx and run it.  It doesn't matter where in the
pad the pScript named xxx resides.  The code Paul wrote into pedit and
pToolSet to run pScripts goes to the very start of the pad and scans
down until it finds {xxx:  and runs it.  If there is more than one
pScript with the same name, the one nearest the top of the pad will
always run, no matter what you intend, because that is the one that
the program encounters first.  You could have the various SPd scripts
scattered all over the place in your pad, not in numerical order, and
it would run just fine.  The sequential numbering is to assist the
user logically, not to run the chain.  So, if you now have two
different {SPd6: pScripts, whichever is closer to the top of the pad
is the one that will run, rgardless of your intent.  You must either
change *all* the names in the chain, or just use "}" to stop SPd6
after "d".  That is to say, in the modified spD6

{SPd6::d
/&script$[@@LeadingSpaceDelete@@]}

if you just put "}"  after  "d", so it reads

{SPd6::d }
/&script$[@@LeadingSpaceDelete@@]}

then you have the original SPd6, it will stop at "d" and not run /&script$....

Then you would not need a renamed SPdelete at all.


> but the set of scripts you made make a pretty good 'web page sanitizer'

Great!

      ~ John