Previously posted question......
PROCESS TEXT : testCards - > I finally found time to create an example you can test -> attached below
run the project example
click View
select a card item to Manage
click Manage
Manage Page/Panel will show
{{Don't worry about changing stuff it won't do anything
The object being to test the return to the Viewing page}}
In the log you can follow the Card index numbers as you flick through the database, something like ->
PageChanged : old index 0 new index 0
PageChanged : old index 0 new index 1
PageChanged : old index 1 new index 2
PageChanged : old index 2 new index 3
PageChanged : old index 3 new index 4
Click the "return" arrow at the top left of the Manage Panel
which will return you to the Viewing Panel
At which point the log shows as follows ->
PageChanged : old index 0 new index 4
Error occurred on line: 486 (AS_CardSlider)
java.lang.IndexOutOfBoundsException: Index 5 out of bounds for length 2
at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
...
...
...
{I have tried forcing OldIndex to be NewIndex - 1 -> but that doesn't work }
At this stage the project has called PageChanged on its return (doesn't need to go to Page_Appear its already loaded)
But as one can see the values of OldIndex and Newindex are not consecutive. In this case (my example run)
one expects that they should be 3 and 4 respectively.
The main point being that when one returns to the Viewing Page/Panel one wants to be able to carry on scrolling around
the database so that another card to review/manage can be selected.
As in the previous question I posted, the issue is about moving between the two Page/Panels and preserving the state of
of the cardSlider and its indexing.
If anyone finds a solution I'd be grateful since this would allow me to set the project up so that users have less
menu clicks (I could eliminate at least two menu buttons and so on etc..)
Thanks for your attention guys......
PROCESS TEXT : testCards - > I finally found time to create an example you can test -> attached below
run the project example
click View
select a card item to Manage
click Manage
Manage Page/Panel will show
{{Don't worry about changing stuff it won't do anything
The object being to test the return to the Viewing page}}
In the log you can follow the Card index numbers as you flick through the database, something like ->
PageChanged : old index 0 new index 0
PageChanged : old index 0 new index 1
PageChanged : old index 1 new index 2
PageChanged : old index 2 new index 3
PageChanged : old index 3 new index 4
Click the "return" arrow at the top left of the Manage Panel
which will return you to the Viewing Panel
At which point the log shows as follows ->
PageChanged : old index 0 new index 4
Error occurred on line: 486 (AS_CardSlider)
java.lang.IndexOutOfBoundsException: Index 5 out of bounds for length 2
at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
...
...
...
{I have tried forcing OldIndex to be NewIndex - 1 -> but that doesn't work }
At this stage the project has called PageChanged on its return (doesn't need to go to Page_Appear its already loaded)
But as one can see the values of OldIndex and Newindex are not consecutive. In this case (my example run)
one expects that they should be 3 and 4 respectively.
The main point being that when one returns to the Viewing Page/Panel one wants to be able to carry on scrolling around
the database so that another card to review/manage can be selected.
As in the previous question I posted, the issue is about moving between the two Page/Panels and preserving the state of
of the cardSlider and its indexing.
If anyone finds a solution I'd be grateful since this would allow me to set the project up so that users have less
menu clicks (I could eliminate at least two menu buttons and so on etc..)
Thanks for your attention guys......