Hi there,
The Global field value dissappears in Find Mode
How can I restore it in Find mode. Since I use global field as labels for buttons in Find mode
Thanks
Hameed
Hi there,
The Global field value dissappears in Find Mode
How can I restore it in Find mode. Since I use global field as labels for buttons in Find mode
Thanks
Hameed
I see some potential problems using global fields as button labels in general since global fields can have different values from client to client.
If you are trying to customize a find form for a particular situation on the fly, could you do this instead?
if (this_situation == whatever)
{
elements.button_name.text = “click me”;
}
Hi david,
Thanks for your reply.
The global fields I use for the button labels are not supposed to change. So I do not see a problem. The global labels would be set only during the application startup and that’s it.
I use this approach in filemaker as well.
The reason is for example if I have a button that takes you to the find mode, I want to call that button for customer A as “Find”. If I do a similar project for customer B with some little modifications, and he wants to call that button as “Search” instead of “Find”, all I need to do is just change the script that is setting the global labels. I do not need to go to each and every layout to change it. That’s why I use this approach.
It works perfectly with Filemaker globals. They don’t dissappear in the find
mode.
Any help would be highly appreciated.
Thanks a lot.
Hameed
in the search globals and other vars will be deleted yes. We will look into this to keep it somehow
You dont have to use globals to change the text. You can also use a label and set the text of the label by scripting, at startup of while running your solution
Paul
faheemhameed:
I use this approach in filemaker as well.The reason is for example if I have a button that takes you to the find mode, I want to call that button for customer A as “Find”. If I do a similar project for customer B with some little modifications, and he wants to call that button as “Search” instead of “Find”, all I need to do is just change the script that is setting the global labels. I do not need to go to each and every layout to change it. That’s why I use this approach.
It works perfectly with Filemaker globals. They don’t dissappear in the find
mode.
As a few developers have pointed out. It’s not advisable to directly translate FileMaker Pro work-arounds over to Servoy. The Servoy environment is so much more rich that you should control text size, font and color using the properties of an object rather than using global fields.
Any object that has the text, foreground color and font attributes can be changed by a WIDE variety of circumstances.
When you leave, enter, change a field or form you can adjust the text. I’ll work on doing an upcoming video that will show how to change the color of the text on a button relative to where you are in an application. This will show you how to control button states.
Good point Matt,
I understand that I can set the labels of buttons dynamically during system startup or as I like.
Thanks for pointing it out.
Hameed