All of sudden below error is coming while doing gulp build or gulp serve.
A tuple type element list cannot be empty.Error – typescript – src/webparts/displayStateInformation/components/DisplayStateInformation.tsx(14,4): error TS1122: A tuple type element list cannot be empty.
I just sat down to do a typical grab-bar sliding panel, this in iOS ….
being completely familiar with every little widget in iOS I started to type for autocompletion .. grab .. slide .. bar .. but …. what?
On second thought, it occurred to me I’m pretty sure ….. there is no native grab bar element in iOS. No, really!
Three questions arising,
Can anyone absolutely confirm that, uh, there is no native grab bar element in iOS
An interesting question is, what or where is the definitive current list of native elements available in iOS? (This would have application to programmers, managers, etc.) (It would be good to have this for the other major platforms also.)
The only thing I could really find was, if you hunt around on Apple you can download a file UIElements+DesignTemplates+Guides.sketch , but it doesn’t really seem definitive.
You’d think there would surely be a page somewhere from Apple “Here are the and only the native UX elements in iOS”
Funny thing, I swear there are a number of major apps (so, the major social media, etc), for iOS, that use such a grab bar on a sliding panel – can anyone think of an example? It’s on the tip of my tongue but searching around I can’t find one.
Note that iOS has these two sliding-panel-esque elements – I found them in the file mentioned above – but they are indeed grabbarless (unless there’s an option or such I have not stumbled on – again it’s weird there’s really no “definitive list”)
In a min heap of n elements, the Kth smallest element can be found in?
O(n) O(nlogn) O(logn) O(1).
According to me ans should be O(n), say we can have a case where k=n, then we can only find the smallest element in the leaf nodes, which will contain n/2 elements and we need to search O(n/2), i.e. O(n). Is my approach correct?
I am used to working with SharePoint on-premises environments, but I am now trying to come up to speed with SharePoint Online. I can connect to my tenant using Connect-SPOService and use the standard SharePoint Online cmdlets, so my credentials are working and that route of access seems to be in good order for me.
However, I will need to use the greater utility of CSOM for work that I need to do. Initially, I have just tried to set up a simple PowerShell procedure to start walking through some of the basics using CSOM with SharePoint Online. But I continue to have a problem with ClientContext.ExecuteQuery. It always fails with the “root element is missing” error. I’m not sure if this is due to the query not retrieving any data or something else relating to my environment.
I currently have my own SharePoint tenant with some initial sites and lists. I am the only user and administrator. Everything is still very simple. I have installed and imported (using PSGallery) the following modules to set my PS environment (and sessions). I think that I have identified everything that I need, but it’s certainly possible that I am missing something important.
I am working in Windows 10 with PowerShell 5.1 (running as Administrator). Everything is still very simple, but I can’t get past the query execution to load the web context so I can start trying to do additional things.
I have found many online examples of PowerShell/CSOM to connect to sites and set context. I’ve tried them all (at least it seems like I have), but nothing has worked so far. I can’t find anything else to try or additional diagnostic steps to take. So I would welcome any suggestions at this point.
Here is a PS Session Log of one of my test runs with the error message at the end …
The user is trying to select an element which will be used in a form. So it could be like selecting interests in an app where you can pick the more general case (e.g. sports) or the more specific (e.g. baseball).
I have hierarchical data where: * Exactly one node may be selected. * Users can select nodes anywhere in the tree * Leaf nodes must be selectable * Parent nodes may be selectable. Selecting a parent node represents a selection of all of its leaf node descendants. * Selectable parent nodes are uncommon. * The depth of the data is deeper than can be readily shown on the screen all at once.
I am developing an interface for browsing this data. This data needs to be usable on both desktop and mobile interfaces on the web.
I am thinking of modeling an interface after what Apple does with hierarchical menus, like the one below. The differences in my case are primarily that: * The items can have three states: selectable node, refinable node, and nodes with both capabilities. How do I make this look uncluttered? * My design must operate reasonably on both desktop and mobile. How do I design the refinement signifier in an unobtrusive way that is clear even on desktop views. * My lists have a lot of heterogenous content. This happens only rarely in Apple menus, like the shut down button in the second screenshot. How do I show heterogenous content without looking disjoint?
Notice the blue row at the bottom representing differing content.
What I’ve been thinking of so far is similar to the Apple design. These next two screenshots show the top level of the hierarchy here, and…
…the screen after food is selected.
I like the multi-screen approach to this design for my use case, so I am primarily looking for feedback on exactly what icons/buttons to put in, and how to separate out content. I’m particularly interested in examples on the web and high fidelity mock examples, but I’m open to lower fidelity feedback as well.
The one structural thing that I think could be changed is in the combination case where a parent node can also be selected. Conceptually I’ve illustrated it here:
I’d like to draw attention to the fact that this makes the rows less crowded, and seem more homogenous. But I’m not sure exactly how to design the current level selection mechanism. How could I clearly indicate that the current level can be selected? Relatedly, how do I indicate the situation where the current level can’t be selected?