I am upgrading one of my customer's applications to Xcode 9 / iOS11 and I was trying to get large titles to work. They look absolutely fine but I run into several problems when I am popping a view from the navigation stack.
The root cause seems to be that I nest a UITabBarController sometimes to have a row of options below the screen. This is advised against but it used to work like a charm. It still works fine whenever I leave the titles to the old style.
There's a possibility to have large titles in this set up or should I replace the UITabBarControllers with something I custom create that has a UITabBar at the bottom and mimics most of what the UITabBarController does.
Related
I do not use autolayout. My app is incredibly dynamic, in that users can drag fields onto a canvas to create forms. Therefore, I have developed my own routines to render my xibs on any device in either portrait or landscape. To do this, I make sure the Use Autolayout is not checked for the xib's view in the file inspector. In fact none of the boxes are checked (trait variations, safe area, etc). However, I continue to get constraint errors. Is this just a bug. My code works perfectly but it is quite annoying to get the plethora of warnings in the output window. This just started in the last release or two. I am using XCode 9.2 with a deployment target of iOS 11.
Pattern for pagination is currently on a after 1.0 roadmap for Meteor. Are there any examples or suggestions how to do it now? So how to nicely do an infinite scroll by subscribing to new and new elements as user is scrolling to the bottom?
I recommend that you try my package, Pages: https://github.com/alethes/meteor-pages
It's extremely easy to use (you can set it up with just one line of JavaScript), yet very customizable. It features: incremental subscriptions, local cache, neighbor prefetching, request throttling, easy integration, multiple paginations per page, bootstrap 2/3 styling, failure resistance, built-in iron-router support and a lot of settings that can be modified on the fly, without reloading the page.
There is a package on atmosphere.meteor.com for pagination that should get you started
https://github.com/egtann/meteor-pagination (Pagination)
https://github.com/tmeasday/meteor-paginated-subscription (Pagination with publish)
The second one actually sends down one page of data at a go instead of all the data at once so if you have loads of data it might help with that. With the infinite scroll you would have to attach a manual scroll listener and put in the new data by increasing the size of a page as you scroll down (not specifically moving to page 2).
I'm a bit unsure on what pattern to use specifically because using page size might be a bit troublesome unless you're able to get it to work right with reactivity which should be possible if you're able to seperate your {{#each}} block helpers so that its for each scroll down, perhaps using Meteor.render so that the entire set of data already available isn't re-rendered.
It might also work if you put the data in div block containing a scroll overflow instead of the above so that it does re-render but their position in the scroll remains the same, in effect making the re-render unnoticable.
I have a D6 site that I've just stumbled upon the fact that my block positions are no longer being updated. I have a given block (a Views block) that works on older pages but not newer ones. I've tried creating new blocks and they do not show up either. Old blocks are where they should be an data through Views is still being populated correctly. My site is in a state of freeze as I cannot apply some blocks to new pages. For example, the products page does not get certain blocks on creation of new products but the old products work fine. Is there someplace I can view what is going on? I've tried clearing the site cache, turning it on / off to no avail. I did notice an odd appendage to the offending block link (I should note fresh blocks do not work either)
(Doesn't work correctly)
http://www.mysite.com/admin/build/block/configure/views/c0e4f6940320aed972444b51a879c490
(Newly created block, also not working)
http://www.mysite.com/admin/build/block/configure/block/12
please try to clear the cache first before taking any further steps
i'm currently having a nightmarish moment with Sitecore. Basically my issues are two-fold:
1) the first time i added a standard value item to a template, and added a layout setup to it, i was thrilled, since all my items from that template were showing the layout, however now, certain items are now showing no layout at all. I tried doing presentation->layout, reset several times, but to no avail.
2) i added a new sublayout to the standard value layout to another placeholder, did publish on the template (republish everything, publish subitems), then publish on the standard values item again, just in case (should not be needed), i click on all items from the template, and they show the updated layout with the new sublayout (should be good, right?) however, i browse, both live and with preview to the pages and i am still seeing the old layout without my new sublayout.
- I added a breakpoint in the page_load of the new sublayout but it never hits, the others do
- I tried cleaning the cache on sitecore/admin/cache.aspx, but did not help
- tried recycling the app pool, restarting the web site, spreading black rooster' blood over the machine, nothing seems to helps
i am using sitecore 6.2.0 (rev. 100701), visual studio 2008 SP1, IIS7 in integrated mode
Basically the way to do it is set layout on the Standard Values, which should update all items, that haven't had their layout overwritten on the item or by a branch.
This is the key to the issue. If your items that aren't getting updated with the template standard value layout were created using a branch, check to make sure that branch does not also have layout details associated with it. If the branch has layout details in addition to the template, the two will conflict and cause really odd, frustrating behavior.
I encountered the exact same scenario, but after removing the layout details from my branch the issue went away.
Sounds strange... usually this only happens, when you have a "conflict" between layout set on Standard Values, template/branch.
Basically the way to do it is set layout on the Standard Values, which should update all items, that haven't had their layout overwritten on the item or by a branch.
I really dislike branches, so always try to avoid them (the only real use when they were Masters were for building hierarchies of items).
Could you try to look in the __layouts field (View > Raw values) of the items and see if anything is entered there?
And is it only some items or all items based on that template?
I am going to write an application that uses QT4 (with C++ or python it isnt important in that moment).
One of functionality is "Showing all items in database".
One item has a Title, author, description and photo (constant size)
And there could be very many items. Let's say 400. There won't be enough space to show'em all at once time.
One row will have 200px, so i need at most 4 for once time.
How to paginate them? I have no idea.
I can use limit and offset in SQL queries, but how to tell window: "that's 5th page"?
Any solutions?
First off, you normally do not want to use any manually set pixel widths in any GUI application, if you do, your toolkit sucks (or you must work in game development).
Second off: be more specific.
You'll need to define "page" for your application, namely what a page should be in its context. I assume it is breaking a list of items into separate pages. Normally this is done by using one of the view classes (e.g. QListView or QTableView) to take care of much of the legwork: it's called a scrollbar (not to mention the collapsing folders concept from file managers). Another method is splitting the information across several tab pages (QTabWidget), where each page displays a view of some sort (Perhaps QTextView or one of the M/V or Item view classes).
Same thing can also be done using your own widget stack and some other widget to manipulate the currently displayed page. This is basically how the option dialogs in the TeamSpeak 3 client and most KDE apps work; it's also how wizards with back/next buttons work in concept. I suggest you take a look at this config dialog example
Normally what you want is a view with a scrollbar and or some form of collapsing related entries into categorised information. If you just want to display a list of pages where each page is X entries: use a tab widget or stacked widget.