## nested boxes algorithm

I am given a set of 3D boxes {$$B_1$$, $$B_2$$$$B_n$$} and each box have length, width and height. But these values are interchangeable since I can rotate the box. I need to find out the maximum sequence of nested boxes.

I have tried this problem using sort. But I still get stuck. I used built in sort function to sort all boxes by length in ascending order. I read the reference about this question and learned that people used radix sort. I have know idea how radix sort is applied here because all sorts I am familiar is comparison sort.

Some fields could be added by default, but not required. Its not a perfect solution, it would me much better to create additional .dat file, where we could define custom types (just like in engine.ini) that can be used for generic fields <- all of them could pop – up in project settings as additional but not required. But they should not be overriden by default Engines data fields ? Its a thing to discuss.

` Facebook_URL`
`Twitter_url`
`about_yourself`

## Check off the boxes you wish to unsubscribe from

In attempting to unsubscribe from a company’s emailing list, I was directed to a website with the following form.

Note the phrase “Check off the boxes… you wish to unsubscribe from.” Is this some type of standard phrasing? The use of the terms off and unsubscribe seem to make the sentence ambiguous; should I check or uncheck? (The default page has all check boxes unchecked.)

Is there a way this company can improve their phrasing?

## Custom Vape Cartridge Boxes

The Custom Vape Cartridge Boxes are aiding the top cosmetic brands to enhances brand awareness effectually. There is variety of cosmetic products each of which has different packaging requirements. Customer satisfaction is our valued priority.

## Custom Bath Bomb Boxes

The Custom Bath bomb boxes are aiding the top cosmetic brands to endorse their beauty and skin care range effectually. enhances brand awareness and drive business sales and this is a fact the way of packaging may attract potential customers and induce them to take a look at your product while showcasing on the retail shelf. The alluring color schemes, styles and extensive designs in packaging can be varied and designed in an appealing way to attract planned consumers….

Custom Bath Bomb Boxes

## Is there a recommended size for search boxes?

Do users change their search patterns if the search is shorter? Do users search less if the search box is too large?

The only article I’d found is a 2009 Smashing Magazine article:

The [Nielsen] study found that the average search box is 18-characters wide. The data showed that 27% of queries were too long to fit into it. Extending the box to 27 characters would accommodate 90% of queries. Remember, you can set widths using ems, not just pixels and points. One em is the width and height of one “m” character (using whatever font size a website is set to). So, use this measure to scale the width of the text input field to 27-characters wide.

In general, search boxes are better too wide than too short, so that users can quickly review, verify and submit the query. This guideline is very simple but unfortunately too often dismissed or ignored. Some padding in the input field can also improve the design and user experience.

## Should alert boxes be avoided at any cost?

Thanks to Gabriel Svennerberg and Sam K for this one – raised in a comment here.

I was fairly casual about alert boxes until a run of user tests where an alert box was put up to warn learners that if they left an online course at a particular point they would lose work they’d already done. Leaving aside the fact that that situation should probably never arise in the first place (! no poka-yoke there), we were very alarmed by what we saw.

Users basically clicked on that alert box in a completely random way, based on their prior experience of alert boxes in other software.

Only a smallish minority of users read the text of the alert box. Most just clicked something: either the button that kept them safely on the page, or the one that deleted their work, or the ‘X’ to close the dialogue. Most were bemused by whatever came next. Digging deeper, it seemed that many people just had a set action for ‘error’ boxes – click something to make it go away.

On that basis, how far do we go to avoid alert boxes?

## Are tabs and/or steps in a wizard displayed as separate boxes in a sitemap diagram?

I’m creating a sitemap for an enterprise application.

For one section in the application, there is an edit calendar feature. Once clicked on, there are three sections/or different types of calendars to set up.

1. Start/end dates for the entire project
2. Blocked-out dates (holidays and nonworking days, etc.)
3. Start/end dates for specific tasks within the project

We currently use a step wizard to edit the calendar so the user has to set up the dates in that order.

In my sitemap, do I draw out each step as a separate box, or would that go in a separate user flow diagram?