I searched around, but dont see how to get the PlanEstimate swipe on the cards in a custom Kanban board.
I have overridden the CardContentRight and then tried to set showPlanEstimate, but not no avail.
I see in the documentation there is a setShowPlanEstimate, but again, not sure where to actually put that code to make it come up.
Ext.define('Rally.ui.cardboard.plugin.MyCardContentRight', {
alias: 'plugin.mycardcontentright',
extend: 'Rally.ui.cardboard.plugin.CardContentRight',
config : {
showPlanEstimate: true
}
});
Probably an easy answer, but I cant seem to show them on my cards. Cant I just set the card somehow to make it show, or do I really have to override CardContentRight to get it to show?
As long as the fields specified on your card contain PlanEstimate and the data being fetched includes this field it should just work without needing to extend the card content right plugin.
Related
I am working on creating an EventPass to be saved to google pay.
I am following this link pass template to create EventPass.
I have succesfully created the Event by Overriding and making a few changes to the layout by using CardTemplateOverride but there are two issues which I am unable to resolve.
1.In CardTemplateOverride I have used FieldReferences of TextModuleData which I had created only for the purpose of showing in CardTemplateOverride. But I do not see a way to hide the TextModuleData which is also showing up at the bottom of the cards.
Could someone suggest a way to hide this textModuleData?
2.In CardTemplateOverride I have used CardRowOneItem, But it is center aligned as mentioned in the document. But my requirement is to have it left aligned and I do not see any option that allows me to do so.
From what I learnt so far the documentation, I do not see a way to do it. But I am not sure.
I have attached an Image Google Pay Event Pass that has been created. The canvas area in the center is a barcode which I have removed just for security concerns.
In the card area we have Date and Time which is referenced from the TextModuleData below the card. But I do not want to show the same information twice. Also the EntryInfo is center Aligned which I could not override and align it to the left.
I inherited a vuejs project. People using screen readers as assistive devices complain that their screen readers are unable to read the options in drop down menus that were made from vue-search-select. Here is how you can reproduce the issue:
Install a screen reader such as NVDA.
Turn on NVDA screen reader.
Go to https://vue-search-select.netlify.app/#/model
Tab to a search text field.
Confirm drop down of results appear.
Press the down arrow key to focus on any of the search result items.
Confirm the NVDA says the word "Blank" instead of actually reading out the contents of the selected item.
Here is a 10 second clip to that demonstrates steps 3 of 7.
https://www.youtube.com/watch?v=Nxx1k1oKETI
How do you modify vue-search-select such that in step 7, the screen reader will read out the contents of the selected item instead of reading out the word "Blank"?
Right now, as a temporary solution, I'm trying to write a setTimeout function that will automatically add the appropriate meta data to force screen readers to read out the content. But I'm not sure how successful this approach will be. I prefer an approach that is idiomatic to vue-search-select.
I tried adding a customAttr like so:
<model-select :custom-attr="ariaAttrs" />
function ariaAttrs() {
return function() { return '" aria-label="hello" tabindex="0'; }
}
Although the attributes do appear in my developer console's inspector, my screen reader still does not read out the options.
It seems custom-attr will not help you as it does not allow you to add any attr you want - anything the function returns is just placed as a value of data-vss-custom-attr attribute
Any decent Vue library with similar functionality would offer a slot to customize rendering of menu items, but this does not. Plus it doesn't seem to be maintained for a long time so maybe it is a time to look for an alternative....
I am nearly done with a custom app that displays a grid of PortfolioItem/Features, and then displays a Kanban board for the User Stories that are associated with the selected feature from the grid. I am using the Kanban board from the app catalog as the basis for this custom app.
As the plug-ins for the Kanban board itself seem kind of complicated, my approach to filtering the stories is to set the query setting to (Feature.FormattedID = "F1234") programatically. I first had to add a name to the query setting in the example's Settings.js:
{
name: 'query',
type: 'query'
}
It only had the type property before.
I then hooked a function to my feature grid's selection event to set the 'query' setting to the desired string using the provided method at the app level:
...
this.updateSettingsValues({
settings: {
query: qString
},
success: function() {
console.log("Query setting changed");
},
scope: this
});
When I select a feature in the grid, I get the log entry showing success, but the Kanban grid content does not change. If I open the settings UI after making a selection I see the expected query string in the 'query' setting text box. If I click the Save button without changing anything else, the Kanban then does correctly update as expected, showing only the desired User Stories.
I have checked the docs for the Settings, and the entry describing the updateSettingsValues() under the Bare Metal section doesn't mention any event to fire to cause the settings change to actually be applied in the app, and I am at a loss as to which event I want to do this. I think I am only one tantalizing line of code away from custom app glory...
Sounds like a cool app! You will soon be immortalized in the annals of Rally app history. All you should need to do is trigger the refresh of the board. Check out the Rally.ui.cardboard.CardBoard.refresh method:
cardboard.refresh({
storeConfig: {
filters: [
Rally.data.wsapi.Filter.fromQueryString(qString)
]
}
});
When I single Tap on list item view gets added twice. Issue is I have to click back button twice to come back on the same page. Anybody knows what is exact issue.
If possible Provide some reference code.
Hi I was facing same issue use below code it will fix your issue.
if (this.getNavigationView().getActiveItem().xtype != "viewName") {
this.getNavigationView().push({ xtype: "viewName" });
}
Good Luck..
I have an issue with a list/detail pattern. I have an Article class, inheriting from QObject, defining some properties (title, updated and content being the ones that matters for now). To populate my (QML) ListView, I have a C++ GroupDataModel, filled with some Article*. Here's my list's onTriggered:
onTriggered: {
if (indexPath.length > 1) {
currentArticle = dataModel.data(indexPath);
var page = articlePageDefinition.createObject();
nav.push(page)
}
}
As you can guess, the articlePageDefinition defines a page using the upper currentArticle property.
Now, when I display the articlePage once, it's working fine. I can go back, click on the same list item, display the same Article details, works great. But when I pick a second article, the app kind of freezes. I can go back in my navigation pane, but I can't click on list items anymore. I tried to add some logs, the onTriggered is stuck on currentArticle = dataModel.data(indexPath);. At this point, I can log every property of dataModel.data(indexPath) without any issue. I tried to not create/push the page, simply affect currentArticle and display some of its properties, it's working fine too. I really don't understand what I am doing wrong here, any help appreciated.
In case you need to see more code, everything is here: https://github.com/Kernald/tt-rss-bb10/tree/e29e3b616aa179dd42f66804ecc20a6a45b6bb22
Here what can cause the problem your are having:
You create the articlePage and bind it's data to the "currentArticle" global variable
When you go back the articlePage is not deleted.
You open an other instance of this same articlePage. The last one still bind its data to the same currentArticle instance.
When you go back and click another item: the previous articlePage still exists in memory. It binds to "currentArticle". The problem is, it's not the data of "currentArticle" that has changed but the object referenced by "currentArticle". The Qml binder just fails then.
I had a similar behavior of my app, but I did not inspect your github code if the reason can be the same. I think you can verify that more quickly than me.
When removing and adding a list item with the same index, the code gets stucked. I removed an entry on user action and added a new one at that place, and it got stuck. This is a known issue to BB10, I found here: https://developer.blackberry.com/cascades/download/releasenotes/#known