Af:processTrain 10g version

Question

Hello.
I am working currently on implementing an ADF/BC-JSF application out of JDev 10g.
I am working with the af:processTrain component; we have a train with about 7 nodes/cars.
I have noticed an something odd, and would lilke to change it if possible.
The component, or maybe even the process menu model behind it, seems to have an associated behavior which is ...
1. initially displays the first n train cars
2. as the user advances to about car 5, then cars 1, 2, and 3 disappear. They stay gone as long as the user advances.
3. If the user clicks on car 4, though, then cars 1, 2, and 3 reappear.
This sort of reminds me of either an iterator range, or maybe the rowsByDepth property for the af:treeTable. I am assuming this is a feature of process train, so that if trains get long, then the train only shows x cars on the page at a time.
So, if this is the case, I do not know if it is possible to change x.
I hope somebody recognizes this behavior, so I can know how to proceed. I am looking at Trinidad source now. I guess I am looking for a magic number around 5 or 6 or so.
If nobody has ever heard of this before, then maybe it is something else I am doing.
Michael F.

Answer 1

Attention: the -ora-visible-stop-count property does not seem to be working as advertised.
Can anybody give me more information? I am on 10.1.3.4.0.4270 of JDeveloper.
Trinidad seems to indicate that this issue I am having is fixed with a statement like af|train { -tr-visible-stop-count: 10; } to increase this default from 6 to 10.
I also see in an svn commit for trinidad that -ora-visible-stop-count was removed and -tr-visible-stop-count was put in its place. So somebody somewhere must have used this as some point???
I af|train should be af|processTrain, since they must have changed the name at some point in Trinidad.
I also notice that af|processTrain with no pseudo-selector (like ::visited, ::active, etc.) is not in the list of valid style selectors. Nor does this process train seem to change its style on my test page when I use af|processTrain with no pseudo-selectors. Since the internal documentation seems to indicate that this -ora-visible-stop-count property is to be used with af|processTrain with no pseudo-selectors, and this property does not seem to do anything like what is advertised or expected, I am wondering if somehow it is not wired up??
Michael F.