Radicore Forum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » RADICORE development » Bug Reports » LIST3 - no paging area for "middle" as of 2.10 (LIST3 - no paging area for "middle" as of 2.10)
LIST3 - no paging area for "middle" as of 2.10 [message #7244] Fri, 07 December 2018 06:15 Go to next message
divico is currently offline  divico
Messages: 16
Registered: August 2008
Junior Member
Greetings,

I noticed that since upgrading to 2.10 the paging area for the "middle" entity is no longer displayed. That problem did not occur in 2.09. I attach two screenshots, one from 2.09 and one from 2.10. The application is the same. Any ideas?
  • Attachment: radicore.pdf
    (Size: 134.83KB, Downloaded 368 times)
Re: LIST3 - no paging area for "middle" as of 2.10 [message #7245 is a reply to message #7244] Sat, 08 December 2018 05:24 Go to previous messageGo to next message
AJM is currently offline  AJM
Messages: 2347
Registered: April 2006
Location: Surrey, UK
Senior Member
Whoops! Embarassed That was a mistake in the stylesheet. Please replace your copy with the fixed version which is attached.

Re: LIST3 - no paging area for "middle" as of 2.10 [message #7246 is a reply to message #7245] Sat, 08 December 2018 07:05 Go to previous messageGo to next message
divico is currently offline  divico
Messages: 16
Registered: August 2008
Junior Member
Thanks that works.
Re LIST3, what I always wanted to implement is:
On my LIST3 view I'd like the children/middle displayed to be the one I selected on a previous LIST2 view, instead of always start with the first record. What would be the best approach to implement this?
Re: LIST3 - no paging area for "middle" as of 2.10 [message #7247 is a reply to message #7246] Sun, 09 December 2018 04:11 Go to previous message
AJM is currently offline  AJM
Messages: 2347
Registered: April 2006
Location: Surrey, UK
Senior Member
I'm afraid the current design does not support what you want. When you press a navigation button in one form in order to call another the items which you selected in the first form become the WHERE criteria in the outer entity/main of the second form.

Instead of having a LIST3 then I would go for another LIST2 where the outer entity shows the child from the previous LIST2, then has a JOIN up to its parent, thus combining two entities into a single zone.


Previous Topic: ERROR CREATING WHERE CLAUSE WHEN USING SEARCH
Next Topic: where2indexedArray failure
Goto Forum:
  


Current Time: Thu Mar 28 10:23:42 EDT 2024

Total time taken to generate the page: 0.01009 seconds