--- In [email protected], Alan Martin <[EMAIL PROTECTED]> wrote:
>
> A few tips which might help:
> 
> Nobody can learn to use all of PowerPro's features in the first month.
> I recommend you leave whole chapters of it for next winter
> or until you really need them.
> That's not being patronising, it's just a reality for all users.
> 
> For example you don't need Menu ShowFile filename.txt or importing
> command lists from ini files for what you are currently working on.
> It's easier to work with the command lists in your .pcf (shown in
> pproconf's Command Lists dialog).
> 
> OK, I agree it was a good idea to try those things when it seemed
> that using cl.SetIcon wouldn't work for your menu
> but actually it will :)
> so you don't have to open those complicated chapters. phew.
> 
> --------------------------------------------------------
> 
> When you use cl.SetIcon() [or cl.Setlabel() etc] to change items
> in your command lists, the item is temporarily changed from
> how it is defined in your .pcf until any one of these happens:
> 
> - you close and restart PowerPro
> - you click Apply or OK in pproconf
> - you change it with another cl.SetIcon() command
> 
> -------------------------------------------------------
> 
> You wrote:
> > ... and the HookWindowEvents variable that carries the caption
> > never shows a caption for a menu so that's out ...
> 
> A menu's not a window so HookWindowEvents won't apply.
> 
> Unlike a bar (which is a window) when a menu is actually showing
> on screen, it is too late to change any of its text or icons etc.
> 
> With a menu, you can change it with cl.SetIcon() before showing
> it and that will affect all subsequent showings of the menu,
> until one of the 3 resetting things I listed above.
> 
> > I have a menu that I want to refresh the icon display each time
> > it is triggered so that the icons will reflect a potentially
> > changing situation.
> 
> If you want a more complicated scripted result from clicking
> a bar button, or menu, or hotkey,
> it is usually easiest to change the command which used to do
> Menu Show mymenu to do only one thing instead: .myscript
> and in myscript.powerpro (for example):
> 
>  If(modem)do
>    cl.seticon("mymenu","itemID","c:\pathto\ModemOn.ico")
>  Else
>    cl.seticon("mymenu","itemID","c:\pathto\ModemOff.ico")
>  Endif
>  Menu show mymenu
> 
> -----------------------------------------------------
> 
> I sometimes wonder whether my long explanations are helpful
> or just boring and unnecessary.
> Maybe the brief answers which other writers make
> would be sufficient.
>

Last things first... some times lot'sa info is good; sometimes short,
snappy answer are good. Most often, if the time to provide both
approaches can be justified, supplying both is ideal. Between you and
Bruce it is pretty hard to miss the point.

As to my approach to problem solving and the richness of PowerPro's
architecture: I am just a shotgun kind'a programmer I guess. In a
production environment, it gets me in trouble and I have'ta watch
myself. Out here, by myself, I can do it any daned way I please :)> I
do take your point tho.

thanx for the input,

evan






------------------------ Yahoo! Groups Sponsor --------------------~--> 
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/JV_rlB/TM
--------------------------------------------------------------------~-> 

Attention: PowerPro's Web site has moved: http://www.ppro.org 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/power-pro/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to