I have a complex Filemaker database with multiple tables and layouts. What I would like to do is to add a toolbar to each layout. This, of course in view of maintainability of my database solution.
Of course, I could create a nice row of buttons (for example in the header of the layout) and copy past this to each separate layout. However, this is not really a great solution from a maintenance pont of view (if you want to change something you need to do so multiple times).
So... is there another way?
I am looking for something similar to e.g., include in php:
<?php
include 'header.php';
?>
Is there such a thing?
Not really. It could be achieved, mostly, with a bit of extra work. There is nothing out of the box, although you might find some samples on the web.
The closest thing in FileMaker is button bar with styles. Even this will not auto-update by default across different layouts.
You can use a webviewer based on a global field.
Another solution for older versionsis to use a portal with records creating buttons and a script which will do staff depending in which row button is clicked.
I am using a Navigation Window which may be recalled by either a push button which should be on each layout (you have not to change it because it only recall the Navigation Window) and/or a Script (I use to put it at the first place, as CMD-1).
Of course, you need to manage that the Navigation Window has to be closed before the navigation and execution of the Script managed by your Toolbar while, at the other side, you may add every other navigation need ;-)
Best wishes
Carmine Iaciofano - Area
Related
I'm currently building an app where I use a PivotControl as the standard navigation. I managed to style the headers now but after some thought I realised that I should probably make the whole app sizeable for different screens. Not every screen (especially in IoT scenarios) will be a full HD screen :D
Thats the current control:
My problem now is that when I make the screen and the PivotItem smaller it just cuts off the end of the pivots like you can see at the right of the picture.
What I would rather have is that when the PivotItem gets smaller I want the Headers to stack.
Like in this quickly googled example:
But I don't know how I should make that possible...
Does anybody have an idea?
What are you trying to build?
Could the content be organized in other way?
Pivots or similar controls (tabs, segmented controls etc) work best with few items that are important to the user and deserve the central stage.
The screenshot you added violates several UI best practices and I suggest you find an alternative to structure your UI that is user friendly.
I am learning XAML/Xamarin Forms, and have been making some initial apps. However, now I am trying to replicate a design.
Quite a lot of apps have a menu such as this:
Or this:
While also having tabs in the bottom of the page (iOS at least).
How is this achieved? If I make a TabbedPage, this adds tabs in the bottom, but adding this kind of extra "menu" - how is this done? What technique is used?
Seems is a segmented control, already exist a NuGet package created by alex rainman, You can take a look on this. maybe this will help you.
https://github.com/alexrainman/SegmentedControl
I am using template 10 for developing a UWP app and i'm using hamburger template so when a user clicks on a particular category i would like to navigate him to a event list in a master detail view where on left is complete event list in that category and on right selected event details.There is a sample provided and its difficult to understand and don't know how to use the sample in my app along with hamburger navigation.Also as an extra feature if the user clicks on a particular category the hamburger panel should hide and masterdetail view of event should come.And when user click on back button the panel should appear again with that page.
If anyone could help me it would be of great help.Thanks in advance.
There is a really detailed sample in the repository. It has 2 examples in total. 1 a control being developed by a community member. The other is a design based around using basic XAML with visual states along with responsive triggers for screen sizing.
I've implemented the response non-usercontrol variant and it works very well. The other control based scenario has some good features and is being updated often for feature additions and corrections.
Master Detail Sample
I think what you might be looking for here is a slightly simpler thing that we are able to give you. Master/Detail is certainly not splitting the atom. That being said, it's not just a drag and drop thing either. Your are going to need to take a look at the sample. Try to reproduce it exactly into a blank project. It's a great resource, but it's not a control for you to use as much as a sample for you to refer to. I certainly wish I had a simpler answer for you, but this is going to take a little effort on your side to understand the mechanics and implement it. In the end, once you pass that "ah ha" moment, I think you will look back and realize it's simpler than you thought. But until you understand how it works at a fundamental level, it's just going to continue to confuse you. I agree with #mvermef that the visual-state approach (the primary approach) is the easiest and uses the skills you will want to learn for future development, too. But, to that end, please recognize there are TWO approaches in that sample. One uses view-states and the other uses a custom user control. If I were you, don't pick the second approach. The first approach will be easy to understand, easy to implement, and wonderfully helpful to understand for other things later down the road.
I'm using Dymola but I expect OpenModelica might very well be the same (or at least similar).
For a given component model sometimes it makes more sense to have lots of parameters shown on one "tab" of the parameter GUI. This can lead to an excessively long GUI which, for many reasons including for psychological reasons in relation to how humans process information, is not a appropriate solution.
To solve this I would like to add a vertical scroll bar on the parameter GUI. I believe I saw it once though I cannot recall exactly where.
For illustrative purposes look to the right side of your web browser window. That gray bar that goes up and down is the scrollbar :). I know, obvious but you never know.
I assume I need to put some command in an annotation somewhere though where and what command I am not sure. For example, I found some reference to a verticalScrollBarPolicy but alas, I can not find any documentation on this.
Anyone know how to do this?
EDIT #1:
Dymola (and Adrian indicated OpenModelica as well) will automatically create the scroll bar when the GUI gets larger than the screen. Unfortunately (at least in Dymola) there is little margin so if you GUI is a fraction smaller than the window the "OK" button will be covered by the ribbon on the bottom of the screen and the GUI will be needed to made slightly larger to make the scroll bar appear automatically. This is a reason why a manual option for a scrollbar would come in handy.
I think additional "tabs" might help?
As far as I know in OpenModelica we have a scroll bar for that dialog windows if the window would expand out of the screen.
As of this posting my understanding based on feedback on this forum, my own experience, and from additional discussions with others there is no current manual control of the GUI (i.e., size, scrollbars, etc.).
Your best bet if you come across issues (e.g., you have a super small 2nd monitor) is to use lots of tabs and keep descriptions very short (which is probably appropriate for most applications anyways).
This is a Dymola and OpenModelica issue not a modelica issue as it is not contained in the modelica specification (as I understand it).
If this changes and I find out about it I'll remove or update this post.
Is it possible to add some links in opportunity navigation pane ? I want to move process (Prospecting (Active), Pre-Quota,...) navigation to marked area.
See in picture what I mean.
No you can't do this. The logic of the process flow is controlled by a workflow which you can change. However, the display within the UI is done by the CRM platform and cannot be changed.
The area that you want to move it to is the Command Bar (it used to be called the ribbon in CRM 2011). This can be customized by adding or removing buttons but nothing as extensive as moving entire sections of the form around. You might be able to mimic some of the functionality of the process flow from custom buttons in the command bar. However, I think it would be unlikely to yield much benefit for the amount of work involved.