Accessibility identifier to a table view section - ios6

I am adding accessibility identifiers to all the elements inside my project so that I can use them when I write testing automation script. However I noticed that the under table view, I have table view section and under section I have table view cells.
I could add accessibility identifier to the tableview and the cells, but not to the table view section. I cannot see user defined runtime attributes section for it.
Has anybody came across the same scenario earlier? Could you guys through some light on this.
Thanks.

Related

Google Data Studio: Filter inheritance options missing

I've asked this question on the Data Studio community page with no response, and haven't been able to find the answer elsewhere.
I need to stop 2 charts on a page from inheriting the page level control that I have set. From searching around, it appears that there used to be an option to disable filter inheritance, which would achieve exactly what I need. However, that option seems to no longer be available.
I've tried manually setting chart level filters that include all of the information I need, but they still seem to be overridden by the page level controls I have set. I've tried creating calculated fields that hard code the information I need, but they are also overridden by the page level controls regardless.
The comparison that I need to make is between an individual store's customer churn, and the average churn for all stores. The report is an overall report for all stores, with the ability to choose an individual store from a dropdown control to narrow down the results, so I can't set it up with chart-level filters as that would defeat the whole purpose.
Does the filter inheritance option no longer exist, or does it not apply to controls? Is there another way around this that I'm missing?
Thanks in advance! :)
Screenshot of the filter inheritance options missing:
No filter inheritance
Example Data Studio report:
Example report
UPDATE: I have figured out a temporary workaround, which is to set up a separate data source that does not include the fields referred to within the controls. However, this is not a workable solution for reports with a number of pages and a number of controls added, as it effectively requires a new data source for every control that I need to exclude (and sometimes that isn't possible).
Group
One way to ensure that the two specific charts (referred to as Excluded_Charts in this answer) are not influenced by Controls (in this case a Drop-down list and a Date range control) is to Group all charts except Excluded_Charts, which would result in the two charts operating independently from the rest:
Right-click on a blank space in the Report
From the drop-down click on Select > All charts and controls on page
Ctrl+Click on both charts in Excluded_Charts to exclude them from selection
Right-click on one of the selected charts
Click on Group from the right-click menu
Additionally, to make sure that the Date range control does not affect Excluded_Charts select both charts in Excluded_Charts and change the default date range from Auto to Custom.
Ungroup
To reintegrate Excluded_Charts back with the rest of the charts in the report:
Select the grouped charts (selecting a single grouped component will highlight all grouped components)
Right-click on one of the selected charts
Select Ungroup from the right-click menu
Additionally, remember to change the default date range of the Excluded_Charts back from Custom to Auto.
Editable Google Data Studio Report (Embedded Google Sheets Data Source)
I seem to have found a solution - the issue is that I was looking at filter inheritance rather than controls. Controls can be limited in scope by grouping them with the charts you want them to apply to.
Thank you very much for your help #Nimantha! I would have never figured this out if you hadn't pointed out that I was referring to filters rather than controls.

How to assign custom class to PropertyGridControl.SelectedObject at design time

How could I assign a custom class (Customer, Order, etc) to a DevExpress PropertyGridControl (or native Windows.Forms.PropertyGrid) at Design Time?
The PropertyGridControl.SelectedObject's dropdown list shows only the other Controls used in the form, but not custom fields declared by me. For instance:
Dim oCustomer As new Customer
I'd like to customize MultiEditorRows, styles, etc at design time to show my object properly.
At runtime it's as easy as:
myPropertyGridControl.SelectedObject = New Customer
Any help would be greatly appreciated. Please excuse my bad english.
At design-time only components that exist on a form can be selected as the grid's SelectedObject. Of cause, you can make your object a Component descendant and drop it onto a form to select it. But, I don't think that you really need this. As far as I understand, you need to generate grid rows at design time to customize them. If so, it's better to use the Rows Page designer to manually add the required rows and customize them.

Bacbone Marionette composing a complex composite view

I am trying to create a page which contains a "Form" and a "Grid". Consider a standard usecase of data filter and resulting data table below.
For creating this kind of page, I am struggling to apply my marionette knowledge.
I am sure I need a composite view for the datatable. But then how do I put rest of the content which includes another potentially composite view for the filtering form content?
I think I need a composite view containing another composite view. But that seems incorrect since composite view dictates that the itemView must repeat 'n' no of times. and here I do not have a repeating case really.
I have read through David Sulk's tutorial, Derrik's tutorials.. But could not apply their thoughts to my problem.
Can someone guide me?
--Vijay

Views, add fields, limited options

I have recently developed an odd behaviour in my views. I am trying to generate a simple view that simply lists all entered data of that content type in a table. I have stripped all bells and whistles from the view to get it working but it just won't.
When I create a new view, I can add the relevant fields for the content type, filters etc. It all works as expected. If I then save and try to create another page view for the next content type, all my fields disappear (including the original fields used in the original view). The only fields available are core fields like content:type, content:title, content:post date etc.
I have checked permissions, display values in the content type, searched extensively online. Most people's issue is the relationship hasn't been established but my view doesn't rely on a relationship, it is a simple display view.
Any help or pointers would be truly appreciated.
Thanks in advance Nelle
Drupal 7.22
Views 7.x-3.7
This is a bug in Views. See this bug report for a work-around (disable Views caching and UI Javascript).
Did you tried to remove filters from new page?
There is an important option when you use the same view to create many pages or blocks :
when you edit a field or filter, you should choose where to apply modifications (For All displays or this page (override)

My WPF ViewModelLocator implementation is failing composition within my VSTO Excel Add-In. Can anyone critique?

Background:
I'm using MEF to help compose an Excel 2007 Add-In (VSTO) that can create an entity from spreadsheet data and a creep requirement exposed a shortcoming in my architecture that I'm trying to reconcile(I am now needing to identify columns on "template load" rather than on "worksheet submit")
I have each of my local entity properties decorated with a DescriptionAttribute that contains the name of the column in my worksheet. On submit, I reflect on these attributes to identify which property maps to that worksheet column and create a Dictionary of pairs that map a PropertyName to a column ordinal. I do this because the Excel COM object model seems to only expose the cells of a worksheet based upon row/column ordinals. Performing this mapping allows my add-in to dynamically locate my properties on the worksheet without having to maintain any static property-to-ordinal map.
So, this was all fine and good...and, as this is a stopgap solution for our business partner while we rearchitect the underlying system, we discussed that this was going to be a very "unfriendly" add-in and everyone was intitially onboard. But now, the business has validation concerns for some reference data that will be showing up in the sheet. We had agreed that validation would be performed on submission, but that has changed to need me to have reference columns bound to validation drop downs that only contain valid values.
The Problem
So now, I've been needing to restructure my View and ViewModel such that the mapping of the columns to their entity properties occurs on loading of the View, and that's where the problems have started. I implemented Josh Smith's RelayCommand from code that he has made available, I implemented Reed Copsey Jr's CompositionInitializer for WPF, and I created a ViewModelLocator to assist my compositioncontainer in locating my ViewModel...but whatever I do, I cannot locate the appropriate ViewModel. I'm a bit strung out on this issue at the moment..spent all weekend trying to fix it, to no avail. Can anyone please help? I'm not a MEF expert. I've dabbled with the MVVM pattern, but I've been outside of C# for the past few years and missed much of its evolution. I think it's highly likely that my problem is fundamental, but I have been staring at my code for too long to find it. Please, help.
The Code
I have begun a post in the Microsoft social forum for WPF where I have already posted the relevant code. If anyone would like me to repost it here, I would be happy to oblige. But for now, I will include a link to that thread. (I included a background in that thread as well, but I'm happier with the one here. You can skip the background I included over there and not miss anything)
http://social.msdn.microsoft.com/Forums/en/wpf/thread/f22f081d-e342-4f4e-af41-600cec68f0cd
I am uncertain whether this will have any impact, but instead of exporting your StopgapViewModel class, create a factory class and export the factory class, like so:
public StopgapViewModelFactory
{
[Export(typeof(StopgapViewModel))]
public StopgapViewModel Instance
{
get
{
return new StopgapViewModel();
}
}
}
Remove the [Export] declaration from the StopgapViewModel class, and give it a go.

Resources