Note this was sent on the 14th… but using the wrong account hence it didn’t make it to the NUG. — max
> On Jan 14, 2017, at 5:26 PM, Tim Nevels <[email protected]> wrote: > > On Jan 14, 2017, at 2:00 PM, Max Morrison wrote: > >> v15R5 standalone and server/client, upgraded from v12, interpreted atm. >> >> First, I’d like to verify a possible change in behavior going from v12 to >> v15… It use to be the case that Tab Controls would maintain the currently >> displayed page across new-record load events, on an input form. In other >> words, an input form is displaying a record with a tab control on page 2. In >> v12 when I click the next record button the next record displays with page 2 >> of the tab control still active and highlighted. In v15 my tab control is >> reverting to page 1. Is this behavior the same for all or just me? > > This is how it has always worked for me, so I think it is standard behavior. > You need to add some code to the “On Load” event in the Form Method. I’ll > outline how I handle this. Thanks for the feedback, Tim. I had thought I’d perhaps been enjoying a special feature. Glad to hear my search in the documentation, that failed to find a feature change, because none existed, is not something to fault the thoroughness of the documentation… recent discussions on the matter notwithstanding. Thanks for your code example too though finding an adaptive work-around <grin> had led to your solution. It was the necessity that baffled me!?… given the magic. :) > ... > > 4D does not reset the value of pageTabControl_l when the form is loaded if > you have the Standard Action for the tab control set to “No Action”. That > allows you to rely on the pageTabControl_l value when moving between records. I’ll have to review on Tuesday… I’m probably mis-remembering now, but it seemed to revert with either option, no action and goto page… which I thought odd at the time, but, in a day of strangeness I had already moved on. Either way, thanks for your experience; having to create a test db Tuesday is less likely. >> Input form strangeness: >> >> Many-table records displayed in a subform are not automatically updating >> after record-change button click (next, previous, etc). The relations are >> automatic for simplicity. The subform operated as expected under v12. Oddly… >> after the next-record button click and record data changes but subform data >> does not, if I activate a different data object or click on a different tab >> of a tab control, the many-records subform data updates. Object methods >> contain nothing related to records, and, tracing shows nothing significant >> to generate the update of the subform. > > I have not noticed this, but then again I would not see something like this > because I have code in my Tab Control Object Method that runs when you change > tabs to load any related records. A pattern seems to be emerging with tab controls and related records… a perfectly logical and familiar 4D mode of operation... if one is not use to unicorns and magical features. Thanks for bringing me back to reality, I think. :) But what to make of the related info loading when I click on other objects, without any appeal to explicit loading in the tab control (no object method at all)? I’ll check in again with trace and find-in-database Tuesday; hopefully reality will laugh at me, and not be off to tea with the unicorn. Kidding aside, thanks for speaking up. >> I feel like I’m missing something obvious but I can't grok it so far... I’ve >> read everything pertinent (I think) from versions 13 to 15 and can not find >> anything that indicates functionality of subforms or relations or input >> forms have changed, such that, an input-form record-change-click no longer >> automatically updates related many-table records in a subform. I’ve >> re-instantiated the subform but no luck. This happens on a number of tables, >> many-to-one as well, multi-tab-controlled subforms too. > > You may have run across a “feature” that older versions of 4D had and this > “feature” was removed from v15r5. Some would call that a “bug” in v15r5. It > really doesn’t matter if it is a feature change or a bug, that’s how it works > in v15r5. So if you want to use v15r5 then you will need to add a bit of code > to your Form Method and to the Tab Control Object Method to make it work the > way you want it to work. > > What’s that old saying… if you’re given lemons, just make some lemonade. :)+ … so, you’re saying I should plucker up, huh?… been looking for some sugar since Nov 9th. Thanks for the delivery. :) Thanks again. max ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
