When you have a Collection view that scrolls horizontally, and you want to scroll programmatically for an item, you call:
scrollToItemAtIndexPath
When your Localization native development region is set to a language that is LeftToRight, everything works as expected.
But when it set to a RightToLeft language, it takes an index path as it counted the index from the last item to the start, so you gets the item you didn't want!
If you then set the semantic property of the collection view to Force Left To Right, it'll work as expected, but scrolls from left to right, and it not what I want...
I've set up an example project on GitHub... Let's see who can solve this!! =]
https://github.com/ybeapps/BugInUICollectionViewForIOS
At last, Apple solved the bug in iOS 11.0
They asked me to test it in several beta versions (Some of them had a frightening behavior)
I'm leaving the question and for reference and for backward compatibility
Related
I'm working on a theme in Sony's Theme Creator and thus far, I'm pretty happy with my theme and its progress...
There is one problem however - I simply cannot work out what a particular element/field is named in Theme Creator and thus cannot change this element/field.
Either that or I have already made the change and it's not taking affect.
Further to this, I have experimented with changing anything that appears to be the right element/field (based on the name), however none have thus far had an affect.
The element/field is the blue parts below - they should be the same color as the bar at the bottom of the screen...
Any help would be appreciated.
Those elements you are referring to should be the "Status Bar" and the "Action Bar" (Top). If you aren't sure which item in the left list corresponds to which element on the right, you can always press and hold the mouse button over the item in the list and it should show up as highlighted in yellow in the preview pane.
Is there any way to get back Object groups in library of Xcode 5 just like it was in Xcode 4.
I don’t think so. However, you can click the little grid/list button at the bottom left to show the library as a grid. If you can recognize the icons, and don’t need the text labels, it makes it much quicker to scroll through the list. (This does not work well for snippets, because they all have the same icon.)
I cannot find any reference to this on SO.. The full message is:
"This application is trying to draw a very large combo box, 32 points
tall. Vertically resizable combo boxes are not supported, but it
happens that 10.4 and previous drew something that looked kind of sort
of okay. The art in 10.5 does not break up in a way that supports
that drawing. To avoid breaking existing apps, NSComboBox in 10.5
will use the 10.4 art for large combo boxes, but it won't exactly
match the rest of the system. This application should be revised to
stop using large combo boxes. This warning will appear once per app
launch."
Any ideas what to do about it?
I made the box in IB, and don't think I did anything special to create it.
I had this same issue. The combo box was in a cell in a table. I changed the row height setting of the table to automatic. But, this gave me an error for not being a valid setting for a cell based table. However, when I reset the table's row height to fixed, the message went away.
More Google searches seem to indicate that this has something to do with the height of the combo box. In my case, the row height of the table increased when I reset it from "Automatic". Perhaps this will give you something to go on.
I had the same error. When I dragged comboboxes out of a Stack View, Xcode messed up their heights. To correct the problem, I added height constraints of 22 to each of them. That caused the warning. When I deleted all the height constraints, the warning went away. The comboboxes didn't revert to the crazy heights they had when I dragged them out.
I've had this forever, but ignored it because I had no idea why it was happening.
From reading the other answers here...
From the storyboard I edited the Combo Box Cell inside the combo box. I changed the Cell Size from Regular to Small and back to Regular.
The problem went away.
I have implemented a slickgrid and activated keyboard navigation.
When the users is scrolling down using the down-arrow key and reaches the last of the currently visible rows, the grid loads a whole new section of rows and places the selection at the top.
My user tests have all included a complaint about this behaviour as they all find the jump jarring.
I would like to implement behaviour, so the grid scrolls just one line at a time, when I press the down arrow while the last visible row is selected.
I was wondering if there might be some setting, I have overlooked, or if anyone has some suggestions for how to approach the task of adding this behaviour.
(the "problem" is the same, when you scroll upwards - only reversed of course)
This is controlled by the doPaging argument in scrollRowIntoView(row, doPaging) (https://github.com/mleibman/SlickGrid/blob/master/slick.grid.js#L2662). There's no setting to control that behavior, but you could easily add one.
It was initially written this way to make keyboard navigation faster since continuously navigating down doesn't have to do as much work as it would have if we were updating the grid on every 'row down'.
I'm using the ListPicker from the latest Silverlight Toolkit on Mango
I've got a long list (100 items) of simple text items to choose between - using single item selection mode.
When I click on the ListPicker it opens up in full screen very nicely, but it doesn't scroll to the current selection.
This is a pain for the user - who typically wants to move from "item75" to "item76"
I've looked through the available properties, events and source code, but I can't see any obvious way to get the list to scroll the current selected item into list when the full screen mode opens.
Anyone got any ideas?
I found this Which may help, i hope it does!
in Depth ListPicker
See on MSDN what some of the events that can be triggered when selecting a Listpicker item and mess around with them, you may find a Very good Solution! :)
There didn't seem to be a way to do this with the current release - but the code is open source.
The current release also has a disadvantage of using StackPanel instead of VirtualizingStackPanel - so it is very slow at displaying long lists.
Instead of using this release, I ended up going with a different list selector http://priyarules.posterous.com/categorized-list-selector-for-windows-phone-7