sa,
I use trailing stops in my own trading where the stop gets tighter the longer the trade has been open with low volatility, so even if the trade plateaus I will eventually receive an exit. It suits some of my trades quite well. I also have a ratchetted stop that adjusts the stop at various points along the way, based on time and/or volatility combined with profitability. It works OK for me but often gets me out of a trade sooner with a small-medium profit even if the stock continues to climb, so its needs some tweaking and/or combining with other factors.
A lot of people have troubles with real time charts having alerts generated on the individual ticks that are compiled together to form the last bar. Again, using a .dll there are a couple of ways to deal with the last bar:
count the number of times a signal has been generated on the last bar, if an alert has been already been made on the last bar, then ignore all future signals until a new bar is formed, or
wait until the bar is complete before generating any alerts at all (this can be achieved in MSFL by ignoring the last bar. When a new last bar starts, calculate the entry signals for the now-closed-second-to-last bar on the chart. It doesn't describe too well in text, it needs pictures, but its easier externally than in MSFL.)
spaceant: is there any trick to tackle it, say with an external DLL to "remember" respective entry prices?
It is possible to some work with Mark's Global Variables .dll, but again, this involves some fiddling around.
Please contact me via skype/email if you want to discuss a custom solution.
wabbit
MS: 6.52 EOD, 7.x EOD, 8.0 PRO, 9.2 PRO w/QC, 10 PRO w/QC & MDK
For custom MetaStock programming : http://www.wabbit.com.au
My SkyPE status : 
My SkyPE account : wabbit.com.au