I normally use two views (split panes) in my jEdit. I also like to use BufferTabs. On my last computer I was able to have one BufferTabs section below the tow views from which I could change both view (depending on which was active). Now with the new installation I have a BufferTab for each view.
Does anybody know how to get the single BufferTab back?
I use jEdit and BufferTabs for ages and to be honest, I've never seen the behaviour that you describe. If you are really sure you have seen this behaviour, do you by chance still have your settings directory of the old computer around?
Related
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
Our app is build on wxWidgets and designed to work on two displays. Each display has one wxAuiNotebook which in turn have one wxGLCanvas that we're rendering to.
I'd like a hotkey to be able to switch the two wxGLCanvas windows, so the user experience is that the canvas that was on Monitor #2 is now rendering to #1 and vise versa. (There are a bunch of toolbars and widgets surrounding the canvases, but I don't want them to switch displays.)
wxGLCanvas is a subclass of wxWindow, so I'm guessing it can happen at the level. What functions calls should I be looking at to accomplish this?
Sorry about the vagueness of my question. It aligns with my level of understanding of wxWidgets.
You could indeed use Reparent(), but for two wxGLCanvases it would make much more sense to simply use pointers to them in your code and just flip them when you want to switch them because it's just their contents that matters and not the windows themselves.
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.
I am doing some Coded UI test.
I want to generate a UIMap class for the page under test.
Is there any efficient way or tool to do this? I don't want to click all the controls on the page one by one.
Thanks.
This sounds like a good idea, but probably isn't. Any given 'page' or grouping of controls... could really be tens or potentially even hundreds of UI elements. The actual controls that the user could interact with might be very small.
You wouldn't want every label and every border etc mucking up the available options. So while it's a pain to click on each control in order for it to show in the map, it's probably best to keep your tests concise and robust.
Also, if there are a whole bunch of controls the user actually interacts with on one 'page,' I would even suggest creating separate UIMaps for sections of the 'page.'
This is not a good idea at all. You will want your CUITs broken up as much as possible. If you put every control in one UIMap the map can become way too large causing added time to debug the simplest things.
The other reason to break up your CUITs into separate UIMaps is because if something happens to one of the controls in the UIMap (say you accidently deleted it) and you cannot fix it, you will need to start over from scratch! Much easier to redo a couple of controls rather than the entire page.
I notice that Mail.app, iTunes and even Finder have a similar template, with a various columns, but often, a left Column with "folders" and "files". Is this a sort of standard template, that I can use so as to not reinvent the wheel?
Thanks!!
No, Apple does not provide a control that acts like a finder window, etc., although it is a common request and you might want to file a bug report at http://bugreport.apple.com making this request...it would help push them along to provide such a standard control.
However, there are several controls that implement various aspects that you may want to take a look at like NSTableView, NSOutlineView, NSCollectionView & IKImageBrowser.
Although, to get everything you want, you may have to reinvent the wheel. I have generally found these control hard to customize if they do not provide everything you need out-of-the-box...but they do provide a lot out-of-the-box.
Nopes, but you can create your own templates so you only have to reinvent the wheel once.
By the way, you can decompile nibs from some applications by copying two files from an empty nib into them.
By the way, if you decompile Finder's nibs, you see that they are very messy and the sidebar is in a separate nib. I guess they are combined programmatically.
By the way, iTunes uses Carbon nibs while Finder and Mail use Cocoa nibs.
By the way, Mail is soon to be replaced with a new version that has a totally different lay-out.