lag in tab editing

[Gopala Krishnam Raju Ambati]

using fm 21 in samsung book 4 pro ultra 5 have set tab control on a layout when clicking field in layout mode taking few seconds to select the field any1 else having the issue or any reason ????

[Søren Dyhr]

Perhaps the feature is older and included for backward compatibility. Nowadays, developers might prefer using button bars instead of the panelswitch trigger. Consider using the Top Navigation option in the "Part Definition" instead.

--sd

[Gopala Krishnam Raju Ambati]

looking soo nice but edit lag irritating me a lot inspite power machine

50 minutes ago, Søren Dyhr said:

Perhaps the feature is older and included for backward compatibility. Nowadays, developers might prefer using button bars instead of the panelswitch trigger. Consider using the Top Navigation option in the "Part Definition" instead.

--sd

button bar instead  of tab panels ????? will check this now omg lot of redesegining to do will do 

meanwhile please @soren any example please

 

changed from tab panels to button bar smoothness increased but when red button on portal clicked it  closing button popover without close popover in the script now new problem

Edited June 26, 2024 by Gopala Krishnam Raju Ambati

[Søren Dyhr]

3 hours ago, Gopala Krishnam Raju Ambati said:

changed from tab panels to button bar smoothness increased but when red button on portal clicked it  closing button popover without close popover in the script now new problem

The video you made didn't come through, but there is a lot to do with each button's representation - hovering, presseed and focus ... but the most useful feature is the ability to change icon from weddings or wingdings or such as well as text - but take a look here:

https://www.soliantconsulting.com/blog/filemaker-navigation-bar/

...one of the tricks to pick up here is the use of hides in some filler segments to give the right length to each element in the bar.

--sd

Edited June 26, 2024 by Søren Dyhr

[Søren Dyhr]

5 hours ago, Gopala Krishnam Raju Ambati said:

button bar smoothness increased but when red button on portal clicked it  closing button popover

Popovers are not buttonbars, when I was employed as develper, existed house conventions saying that we never should use any buttons except for the buttonbars, and that included even if just one button should be utilized in the matter at hand. If a popover was in question should we use card windows instead. 

Often would we have a kind of understanding as to why these demands were instated, which made us question less ... because somebody else at some point should maintain your code later. 

But, here comes another point in these rules, and they have often been instated, when some "quirking" in behaviour have been observed ... at some point.

So I would suggest that you get to grips with navigation parts in the parts setup. 

--sd

[Gopala Krishnam Raju Ambati]

 we never should use any buttons except for the buttonbars   ----  any specific reason

[Søren Dyhr]

49 minutes ago, Gopala Krishnam Raju Ambati said:

any specific reason

Because, before they arrived as an option in this tool, you had to hover merge fields ontop of a button, if you should have dynamic naming of each button, and probably also if you should set up a system of hides, the case( function to steer these hidings would be very time consuming to set up and debug and likely to make less profit. 

While a scripted setting of these texts trigged by an "on layout enter" trigger just takes a few seconds to code.

https://community.claris.com/en/s/question/0D50H00006dsjVWSAY/how-can-i-display-the-value-of-a-global-variable-across-multiple-layouts

--sd

Edited June 26, 2024 by Søren Dyhr

[rwoods]

Quote

Because, before they arrived as an option in this tool, you had to hover merge fields ontop of a button, if you should have dynamic naming of each button, and probably also if you should set up a system of hides, the case( function to steer these hidings would be very time consuming to set up and debug and likely to make less profit. 

Just as a note, you can use 'Layout Calculations' to define the text for a regular button now, so maybe the requirement to use Button Bars due to their naming flexibility has diminished?

You can just use the <<ƒ:  >> notation in the Button Text field and it will work fine. Sadly you have to hand code the layout calculation, as Claris haven't included a Calculation editor option there, but it's not too tricky.

[Søren Dyhr]

31 minutes ago, rwoods said:

the requirement to use Button Bars due to their naming flexibility has diminished?

It has, but these developer conventions, also dates back to before the pandemic ... the new <<f: just arrived some month ago ... but for teaching purposes, is it pretty good exercise to self inflict a certain limitation, to counter "optionitis" and distractions.

--sd

[comment]

12 minutes ago, Søren Dyhr said:

is it pretty good exercise to self inflict a certain limitation

It is a pretty good exercise in shooting yourself in the foot. There is never a good reason to take any tool out of your toolbox. 

Now, how is all this related to the problem of lag when editing a layout??

 

[Søren Dyhr]

3 minutes ago, comment said:

Now, how is all this related to the problem of lag when editing a layout??

I'm just telling, that there were made limitations to what we were supposed to use as developers - when I was working for a certain developerhouse - and here were traditional tab panels not part of our choises - and what the reason for the instatement then was, should be unsaid. 

But I have noticed this lack of responsivness, because I thought I would use it in a solution I made a few days ago.

--sd

[comment]

15 minutes ago, Søren Dyhr said:

I have noticed this lack of responsivness

Well, I haven't. And I haven't seen any report of such problem until now, let alone a reproducible example. And as an adherent of the scientific method, in the absence of a verified experiment I treat any hypothesis as no more than pure speculation.

 

Edited June 26, 2024 by comment

[Søren Dyhr]

48 minutes ago, comment said:

any hypothesis as no more than pure speculation.

Which it really is ... and it only really bothers the developer, and I expect it to be a css thing because you in layoutmode also would have the transistions as live as possible ... so yes live with it, or switch to buttonbars!!!!

The best song of the band Genesis, was composed by leaving out something deliberately ... but is obviously art and not pretending it to be something in the vicinity of science....

I not consider this to be science at all, but instead a craftmans-ship and exchange of practical expirience in knowing all the rules, and when to break them....

--sd

Edited June 26, 2024 by Søren Dyhr

[comment]

16 minutes ago, Søren Dyhr said:

so yes live with it, or switch to buttonbars!!!!

No. I am afraid you're completely missing my point. Which is to focus on finding the cause of the problem, instead of rushing to act on a hunch.

I also don't consider button bars to be an alternative to tab controls, but that's beside the point.

 

[Søren Dyhr]

15 minutes ago, comment said:

Which is to focus on finding the cause of the problem,

Which is that when the developer switches from browsemode and into layoutmode, where a tabpanel is present, ready for manipulation. 

So without guessing can you pinpoint the source, to what is happening before filemaker gets its bearings? I'm on a M1 mac, OS is Sonoma ... no other apps are open ... and filemaker is fm20 ... what are the chances that OP has excactly same spec's and you opposite that have something that just works?

So come with a plausiple way to diagnostizise this, that approches real science?

I sugested to mimic, the functionality, by switching away from what annoys us as developers! 

--sd 

Edited June 26, 2024 by Søren Dyhr

[comment]

14 minutes ago, Søren Dyhr said:

So come with a plausiple way to diagnostizise this, that approches real science?

Step 1: 
Is it your system or is it your file?

Open your file on another system. And see if your system exhibits the same problem with a brand new file.

If you have determined it is your file, you can proceed to:

Step 2:
Start removing things from your layout (or adding things to an empty layout), until you find the one thing that causes the problem when added, while removing it (and only it) solves the problem.

There may be more, and it could turn out that the real cause is a combinations of factors. But it would be a solid start.

 

 

Edited June 26, 2024 by comment

[Gopala Krishnam Raju Ambati]

22 minutes ago, comment said:

you find the one thing that causes the problem

is there any specific known thing on filemaker layout that causes problem ????

[comment]

8 minutes ago, Gopala Krishnam Raju Ambati said:

is there any specific known thing on filemaker layout that causes problem ????

I am not aware of any such thing, but Søren claims otherwise.

 

[Søren Dyhr]

4 hours ago, comment said:

Søren claims otherwise.

It could be that I in the particular layout I found issues with, where i tried to conditionally reformat a repeating summary field, in splitting mode.... Stacking those ontop off each other with calculated hides only showing one of the repeaters at a time, certainly helped the solution along.

But I saw it once or twice, before being in the ball park with the solution!

--sd