Can AwesomeWM give multiple screens access to the same tagged clients? - multiple-monitors

I have two (identical) monitors connected to the same graphics card, and am running AwesomeWM. The default configuration has nine tags, basically giving me 18 desktops (nine on the left, nine on the right).
I don't really want to divide my life into "left desktop stuff" and "right desktop stuff". Is there a way of configuring AwesomeWM to just provide nine desktops corresponding to the nine tags, so that the two screens can each be configured to display any of the nine, independently of one another?

It's possible to move tags across the screens on demand. So you achieve what you want, you need to modify the taglist to show the tags for every screen (and sort them by name) using the source and filter property. Then, in your buttons section, just add t.screen = mouse.screen in the line before the line that selects the tag.

Related

Visio automatic hyperlink for common label

I have a wiring diagram drawn in visio that contains many wires (lines) spread over several pages. To follow a certain wire, I often have to jump around multiple pages. The wires always have the same text/label even when propagated to different pages. Normally, I use the find-in-files and type in the specific label I'm hunting for.
It would be even better if I could just click on the wire when it goes off page and a hyperlink would take my to the appropriate place on the appropriate page.
I know how to create hyperlinks manually, but there are a lot of signals and I'd like to somehow automate this, hinged by the fact that the source/destination share a common label.
Is this possible?
If you have rules, where the corresponding shape (link) resides, then you can set up the hyperlink via a SETF(Getref(... formula.
Otherwise, you could use VBA to find the corresponding shape by parsing the whole document and inserting the hyperlink automatically.
HTH,Y.

Customize word ribbon bar in office 365

I have been working to add icon group to word ribbon bar but I can not customize it as I want. For an example when I add 3 buttons, it will appear as horizontal direction. But when I add 4 buttons one icon will appear as usual but other three as small icons for vertical direction. Is there a way to solve this problem?
As far as I can tell the Manifest specifications do not allow you to set a fixed icon format or option to stop the group from collapsing the icons as you see when you use more than three buttons in your group.
The manifest specifications require you to that each icon must have three Images elements, one for each of the three mandatory sizes:
16x16
32x32
80x80
https://github.com/OfficeDev/office-js-docs/blob/master/reference/manifest/resources.md#images
So without the option in the manifest to block the group from collapsing it is managed by Office and it seems you don't have any say in this (for now). Let the Program Group know you need a fixed size option, they appreciate your feedback.
Adding button specifications:
https://github.com/OfficeDev/office-js-docs/blob/master/reference/manifest/control.md

Binding to custom built control according to different data

Here's the issue, I build a special book reader/browser (For holy quran), my code behind loads the page and constructs how it should look. and then it should bind that look to a some kind of data-bindable custom control to view it properly. the problem is, the look differs from page to page, so I cannot bind to a certain control or wrap panel.
here's how it generally looks:
The decorative border top of the page is always there at any page, it indicates the part and chapter the viewer is in.
If you're starting a new chapter it have additional image under that decorative border or anywhere in the page (there can be multiple chapters in the same page) something like this
or this:
The normal text is not an issue, it's just a special font, however, I put each individual word in its own text block for reasons of user selection by word.
The issue here is, given the previous information, and knowing how random it is to place the decoration picture or the amount of words (text blocks) per page. how can I bind that to some kind of view to separate the view from the VM and Engine that builds the page.
my past solution was to actually build everything in the VM in a wrappanel built inside a scrollviewer having lots of textblocks and images according to the page. but that's naiive solution. I want to rebuild that in a more professional separated way. I also want to do this for Windows RT beside Windows phone so I need to reuse the code behind in a Portable class library.
I think all you need to do is slightly adjust your current design. So perhaps have a VM that represents the entire content, and that would have a Collection of say Pages or Sections. A second VM would represent the Page/Section, allowing you to create a property for the WrapPanel content (i.e. the words) and another property for the Header and or other things.
In the View you would have the scrollviewer and bind to the main VM collection. Then create another View or DataTemplate that represents the Page/Section.
You should be able to do this is a strict MVVM sense quite easily and it will be dynamic based on the content.
You could even cater for advanced scenarios where each section has a different template/view.

Regions in Croogo

I'm having some problems in displaying elements in different regions.
After installing and using Croogo for a while, I made several trials
adding custom elements and custom menus. If I choose region
'right' (being the default region for elements used by Croogo once
installed) everything is fine and I'm able to add anything I want
without any problem.
Anyhow when I choose any other region to display my element (header,
footer, left) nothing is displayed (looking at the source of the page
I noticed the element is not even rendered).
Am I missing something? How can I actually use different regions to
display elements/blocks?
I'm also a bit confused about the 9 regions (named regionX with
X=[1,..,9]) available along with header, footer, left, right. What's
their purpose? Do they actually represent a region on the screen or
they have been left not configured?
Any help will be greatly appreciated.
You probably need to adjust your theme.json so that the desired regions is loaded.

GWT using Activities and Places when screen layout changes per place

My understanding of GWT's Activities and Places is that for a given region on a screen you have an ActivityManager and an ActivityMapper. You can have multiple regions on the screen which means you can have multiple ActivityManagers and ActivityMappers (one per region). So, whenever there is a PlaceChange the ActivityManagers ask their respective ActivityMapper what activity it is supposed to be showing given the Place. This works great as long as your Places all have a common layout that they reuse in different ways to perform different activities. My question is how do we handle the case where different Places use radically different layouts? My first thought is to just have even more ActivityManagers and ActivityMappers, if the Place doesn't use a particular region then the ActivityMapper for that region will simply return null when we change to that Place. If there is a better way I would appreciate any wisdom.
I found it much easier to use a single ActivityMapper/ActivityManager pair for the entire app.
In a typical case you have a "menu" region and a "main" region. The menu region is very basic: a click on a menu item sends a user to a new place. It also highlights the newly selected item and resets the style of the previously selected item. All of this can be easily done in a simple widget that you can include in all views where this menu is required. Having separate ActivityMapper and ActivityManager for the menu region just complicates everything without providing any benefits.
I use the same approach for "top menu" region and "left menu/tree" region: a widget that tells the presenter which data to show in the "main" region.
I have over 50 different places in my app, and it really helps to have a simple architecture: each place corresponds to one view and one activity.