Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions routes-defining.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ After this there are two properties which can use to modify how routes are handl

`useURL` tells `bigwheel` that the Browsers location should be changed when the section is brought in. By default `bigwheel` will change the url when navigating to sections (`useURL == true`).

If you set `useURL` to `false` then the url will never bed updated and also the section cannot be accessed by manually updating the browser's location.
If you set `useURL` to `false` then the url will never be updated and also the section cannot be accessed by manually updating the browser's location.

In the above routes example if a user went in and typed:
```javascript
Expand Down Expand Up @@ -125,4 +125,4 @@ module.exports = {

As you can see to define multi section routes you just define your sections in an array using the standard form or using a section descriptor. What will happen is that when the route resolves all the sections will be run in tandem so all `init`, `resize`, `animateIn`, `animateOut`, and `destroy` calls will happen at the same time for all multi sections.

The reason why this is handy is that if you define `Menu` as an `Object` instead of a `function` `Menu` will always be persistent and it can react to sections coming in for instance highlighting the correct menu button in the `animateIn` function.
The reason why this is handy is that if you define `Menu` as an `Object` instead of a `function` `Menu` will always be persistent and it can react to sections coming in for instance highlighting the correct menu button in the `animateIn` function.