DSLR Footage and 10.0.6

Actually it is part of Mountain Lion and how OS X mounts camera cards now. Apple is moving towards camera cards simply being a folder of .mov files to make life much more simple. Just like right-clicking any movie file in the Finder to transcode it without purchasing extra software. It has some bugs in 10.0.6, but with the next bug fix update I expect it all to work very smoothly and consistently.

Notice how you can see the MOVs from the transcoded folder as well as the mp4s in the DCIM. Again this is new in 10.0.6

Right, because it's treating the contents of Highway as if it's a camera or card. You should also get a different display that allows partial clip selections and filmstrip view.

Tom, I think you might have been a bit hasty on being so dismissive to my concerns.
I believe I should have the right to organize my media as I want, and not only as the application thinks is better. Of course I don't want to work off of the only media or only backup, but as I said, by the time you get to the editing bay in most productions, almost any secured workflows will provide you with at least a second backup: during shooting, assistants need to offload card contents so they can be used again (this creates the master copy of the files, as the cards will get erased), then, if they're careful, they'll create a backup of that drive. Then, in order to get the material to you, the editor, and not be forced to buy too many drives, they will probably copy content from the backups they need to keep handy on set to one final bigger drive where all content will reside in a centralized fashion. Of course, if material is too abundant it will be more than one drive. So, if all this is done not by you and the assistant making the copies of the material doesn't not make those copies importing material through Final Cut (he may not have it on set) but by copying at finder level, once the material gets to you in the hard drive you will be using to edit you won't need another copy of your material that does not reside inside the Final Cut Events folder, and then you would only gain time by pointing to aliased media, skipping the time it takes to make yet another copy. (Of course there are other workflows, and it might be you centralizing the media, in which case you can Import through Final Cut for effectively creating another backup).

Anyway, this is just a point about being able to choose which way you want to work.
But this was not my only point; it was also about the application having inconsistent behavior. Of course I don't expect it to know if my card structure is a backup or not. But if it recognizes card structures and always forces copying material from them, I would expect it to be clear about it, instead of this actual situation in which if i select a higher folder containing the cards, it makes me believe it will not copy anything, and doesn't prevent me that because there are card structures inside it will override my settings and copy the material to the events folder anyway.
There was also another point regarding consistency: as Ben and DSvoboda356 pointed, when you import the files by just dragging them to the event, fcp does not recognize they are stored inside a card structured folder (you effectively bypass that), but then the clips you get do not get the beneficial metadata they otherwise do when using the import window; naming also differs...I know it would be difficult asking the app to recognize if a file came from a certain type of folder or not, I'm just saying all of this does not seem incredibly robust.
In the end I find it's not bad having the different options, you just have to know how the app behaves and choose your way of working accordingly. I'm hoping DSvoboda356 posts as well as mine have thrown some light on a particular issue that otherwise seemed obscure: I'm sure some didn't know that by just dragging the clips they do not get camera or reel embedded metadata, or that by using the import option their clips will always get copied to the events folder no matter what they choose.
But hey, if none of this seems noteworthy to you that's fine just hoping it can help others. Cheers

UPDATE for 10.0.8

I thought I'd bring this back here because the update topic is too random.

Anyway. As far as I can tell it works exactly the same way as before. Having said that I don't see it as a bug at all. The issue I have with the way FCP X works with DSLR files is that it doesn't create a timecode track like it used to in FCP 7. Though I suspect this is negligence on Canon's behalf not FCP X's.

So I get around the problem by using Magic Bullet Grinder. I can't say enough how much I love this program.
I really think it should be in every DSLR shooter's toolbox. The ability to batch rename and add a TC track to your files is invaluable IMHO.

"...as Ben and DSvoboda356 pointed..."

No, I never said any such thing.

And because someone's advice/feedback isn't what you want to hear, don't attack them. Just say "thank you" and continue. I don't think Tom was dismissing anything.

That said, bring on the negative karma, like it matters anyway. "Negative" karma on a site that warns folks not to be "negative" towards each other...

I had this problem today at work while trying to import Canon 5DMarkII media to FCPx 10.0.8, if I used the Import Media window I had to copy the media to the event folder without keywords because those options where grayed out. If I just drag the .mov files from the finder to the keyword collection in FCPx I have all the options available.

I´m trying to replicate this at home with media shot with a P&S Canon S100 which records only .MOV files and a Canon T2i which records .MOV and .THM files. And when I try to import media I have all the options available.

The only thing I can think right now is that the Mac from work has FCP7 and FCPx installed (only FCPx at home) and the Mac from work has all the XDCam drivers and apps installed and the Canon EOS MOVIE Plugin-E1 for FCP7, at home I only have the latest XAVC drivers for FCPx 10.0.8.

I´ll bring a folder from work on Monday to check at home if they work the same way in both places.
Also I found something weird... I copied all the camera structure to my desktop from my Canon T2i, so the DCIM folder was in my desktop, when I tried to import media, ALL the graphics/video files in my desktop (even inside other subfolders) where available to import without folder structure. I changed DCIM folder name to a random new name and I could browse the desktop as "it should be" with just a few folders and files inside.

Dragging from the Finder FCP is only seeing .mov files.
Pointing the Import window to a "card" folder structure, FCP (OS X actually) is looking at a camera car.
FCP (OS X actually) sees the two entities differently.
It is an evolving thing Apple is working on in how the OS deals with files vs camera cards.

Having FCP 7 on a system in no way effects how FCP X works.