I searched and found some solutions for this but none of them seemed very attractive.
When a view is paged, the previous selections in the column check boxes are lost.
Has anyone come up with an easy way to keep the previous selections.
This is a really annoying feature of viewpanels, any chance it will be fixed in the futur?
See http://hasselba.ch/blog/?p=1062 for an xSnippet that will do what you re asking for
var viewPanel = getComponent("viewPanel2");
viewPanel.getSelectedIds().toString();
It wil return the NotesID of the selected Documents.
Related
Is there a way to expand Rows in Datatable by Bootsfaces? I'm sure I already saw this example in the show-cases, but I can't find it now anymore:
https://datatables.net/examples/api/row_details.html
Add the responsive="true" attribute to your b:dataTable:
If there's not enough screen estate to display the table, the last couple of columns are hidden
Those hidden columns are "moved" to row details.
See:
https://showcase.bootsfaces.net/forms/DataTable.jsf (scroll to "Responsiveness")
We didn't implement this feature yet (apart from the special case of responsive="true"). However, you can use the JavaScript code shown on the datatables.net page to implement the feature yourself. The only tricky part is how to get the additional data. I guess the best way to achieve this is adding invisible columns to make sure the data is available in the HTML page.
I have to fix the problem in the title and after one day of research I realy don't know what else to try, what else to google ;)
The topic is discussed in an IBM TechNote.
But this answer isn't enough for me. I really need a workaround!
My question: Can I 'get between' the User clicking the 'Copy as table' and the actual copying of the table?
I see two ways of solving my problem (I don't know how to implement them):
If I just could show the user a Messagebox 'Use our own export agent' that would be great.
If I could convince Notes to just copy each document only once that would be even greater.
If I should make my question more precise, just ask. I will gladly edit it!
Every answer would be highly appreciated. Out of the box thinking, other approaches, I like to hear your opinion!
Friendly Greetings
Josi
Unfortunately there is no way to hook in and alter the results of the Copy Selected as Table method. If it is possible to show an "Export Friendly" view that is not categorized, that is one way to solve the problem.
I'm not sure how useful it will be to you, but many years ago I wrote a sample project for exporting views to Excel, and that should handle categorized views properly. There are surely other options available by now too (though I'm not familiar with them).
I am new to WayFinder but I have been working with it a bit and it has worked great for me, However I need something a little more dynamic that I'm not sure how to do.
I have a set of 5 pages in my website and each page has another side menu, but each menu for all five resources will be slightly different
I need wayfinder to detect what the current ID is and then display the appropriate menu
I've tried a couple things but nothign i can get to work:
[[!If? &subject=[[*28]] &then=[[Wayfinder? &startId=27&excludeDocs=28,29,30,31,32,33,89]]]]
So I need to say if the ID is = to 28 display this menu if the ID is = to 29 display this one and so on.
I've also tried &idIs=28 and a couple other variations but couldn't really find anything to help me out on this Does anyone else have any ideas how to make this work? Thank you.
With the solution typeset suggest, wayfinder will be called each time thereby causing uneeded loading time to your site. This will be faster because wayfinder only will be called when id = 28.
[[[[*id:is=`28`:then=`Wayfinder? &startId=27 &excludeDocs=28,29,30,31,32,33,89`:else=``]]]]
Read more on it here: http://modx.com/blog/2012/09/14/tags-as-the-result-or-how-conditionals-are-like-mosquitoes/
You can use output filters for conditional calls. Documentation for them is here
You code would looks something like this:
[[*id:is=`28`:then=`[[Wayfinder? &startId=27&excludeDocs=28,29,30,31,32,33,89]]`:else=``]]
If the menu needs to start from the current ID then you'd use
&startId=`[[*id]]`
If you want it to show all the resources in the current folder, you can use UltimateParent, so
&startId=`[[UltimateParent]]`
Hope this helps!
This should work. The subject is just the parameter you are comparing it against so it shouldn't contain the value.
[[!If?
&subject=`[[*id]]`
&operator=`EQ`
&operand=`28`
&then=`[[Wayfinder? &startId=`27` &excludeDocs=`28,29,30,31,32,33,89`]]`
]]
Figured it out. LVIF_STATE should have been LVIF_IMAGE. See, I knew it was elementary...
I have a CListView derived class with an OnDoubleClick() handler in a VC++6.0 project. I need to persist the highlighting of the selected item after the OnDoubleClick() handler has done its thing. I had thought that
GetListCtrl().SetItemState(m_nHighlightIndex,LVIS_SELECTED, LVIF_STATE);
would do the trick (assuming that m_nHighlightIndex holds the index of the selected item), but no combination of that and various attempts to invalidate the client area has worked, in either OnDoubleClick() or OnUpdate(). This seems like such an elementary thing to do, but thus far it baffles me. Any help would be greatly appreciated.
Just so it looks answered (and apologies if this is bad form):
LVIF_STATE should have been LVIF_IMAGE. See, I knew it was elementary...
I have a FormsLib with a couple of xml files in there. When I pull up either InfoPath or the standard EditForm and clear out a value on the SPListItem (sync with the xml file) the old value comes back. If I add a space it works. I have tried it via the OM also and the result is the same.
So, for example, if I have a field with the value "Johan" and I pull up the form and clear out that value it still says "Johan" after the update.
Anyone else had any experience with this?
Yes. I have encountered this and the work around I came up with was to add a single space instead of clearing out the field entirely. In my experience though, it only happened if I made the changes in the EditForm. When done in InfoPath, it seemed to work.
Of course, after using " " as my empty value, I had to trim it whenever I needed to check if the field was indeed blank.
I have found an alterntive solution to this issue and I have blogged about it:
http://johanleino.wordpress.com/2009/08/24/node-demotion-does-not-work-with-blank-empty-values/