Mac OS X Lion Discussion


Recommended Posts

Like I said - for applications that don't have the animation type defined on their windows, Lion chooses one I'm guessing based on the window type. I'm guessing the animation type hasn't been explicitly set of those applications yet.

What exactly do Safari, Disk Utility, TextEdit, Automator and dialogue windows (for example) have in common that they share the same type of animation that others don't?

They're scaling in windows from the document/folder you double-clicked on, just like Finder in 10.6 and lower does. This behaviour (window animating from the icon) is now present in document-based apps - I've seen it applied to some non-Apple document-based apps as well.

Yeah, I came that far myself. The issue I'm addressing is that not all document-based applications show the same behavior: TextEdit doesn't do the scale animation, but the "pop". Beyond that a Finder window isn't a document window to begin with, yet it scales. So once again, there's no consistency at this point from the end-user point of view.

When it comes to this Apple just should go the Microsoft route: Give all opening and closing windows one type of animation. Maybe two if all document-based applications scale and the rest "pops". Leaving the choice to developers on a per-application basis just creates an inconsistent mess we're seeing today. This should be global, like the minimizing animation: You don't see this application minimize one way, while another minimizes differently either.

Right now you see windows do nothing, pop, scale and/or appear (from transparent to opaque). It makes no sense to have so many different effects. Obviously the OS is still in beta-stage and hopefully this get fixed before Mac OS X Lion hits GM. Regardless, I think it's a bad idea to have to many different choices. Not to mention there's no window closing animation, except for the Finder.

It?s not going to be destructive if they use Microsoft?s way.

You're repeating what I already said: Microsoft uses one way to address the non-destructive cutting issue, Apple choose another.

Like you say, I?m still waiting for new major features. The ones we know are all so well implemented in Lion that we barely even see them :laugh:

There are no major new features because most of the features are under the hood changes such as writing a SMB2 compatible stack from the ground up - I don't know about you but I don't give a crap about new features, I'd sooner pay over the bucks and get something that works rather than something with the gee-wizz factor to keep the ADD people's attention.

On another note, I feel special because I reported a few pages ago the French voice speaking in DP1, which wasn?t present anymore in DP2, and now it?s back in DP3 and makes the press on some websites. Nuance voices are all included, and are usually featured at $15/voice or language pack. Just this partnership alone can make Lion cost $129 or even a little more.

It will be interesting to see how they go about selling it consider they're going to offer AppStore version - is there going to be a slight premium on the physical copy? I guess only time can tell.

Edit : Can you guys post a screenshot like this under DP3 ? I suspect the following one was falsified, because my build didn?t support it all the way to 3.2

Because you're doing it wrong - you have to choose from one of the menus (can't remember which one) where there is your ordinary video card then there is your video card with some words afterwards which force 3.2 detection.

Because you're doing it wrong - you have to choose from one of the menus (can't remember which one) where there is your ordinary video card then there is your video card with some words afterwards which force 3.2 detection.

Are you talking about choosing "Forward Context"?

attachment.php?attachmentid=285397&d=1305484935

Seems like a gimmick to me? I don?t understand what it does :unsure:

You're repeating what I already said: Microsoft uses one way to address the non-destructive cutting issue, Apple choose another.

The current Apple?s way sucks IMO. Everybody knows about CMD+X and CTRL+X already, why did they have reinvent the wheel once more ?

At least I have this 10-years-awaited feature. I?ll just have to learn and memorize the shortcut?

Are you talking about choosing "Forward Context"?

attachment.php?attachmentid=285397&d=1305484935

Seems like a gimmick to me? I don?t understand what it does :unsure:

OpenGL 3.2 has to be invoked by the developer, you don't get it automatically. All the drop down menu is to force GLView to read the OpenGL 3.x implementation and thus you get the results hence the reason that OpenGL 2.1 is still be optimised as well as OpenGL 3.2 as well. OpenGL 3.2 doesn't replace OpenGL 2.1 but expands upon it hence the old OpenGL 2.1 still remains even in the light of the new OpenGL 3.2 is provided.

The current Apple?s way sucks IMO. Everybody knows about CMD+X and CTRL+X already, why did they have reinvent the wheel once more ?

At least I have this 10-years-awaited feature. I?ll just have to learn and memorize the shortcut?

I gave a possible reason on page 99: Possibly to prevent people from accidentally hitting cmd + X and to prevent destructive cutting (like what can happen with cutting in general). Microsoft choose one route Apple another.

Just awful having to memorize cmd + option + V... Life's such a bitch sometimes... ;-)

I just installed DP3 on my MacBook using Software Update, and it has the proper "Mission Control" text in System Preferences. So even though the build hasn't changed, seems Apple has fixed this issue.

Makes me wonder if I can re-install DP3 via the App Store and get the fix on my iMac.

Can someone copy FrontRow.app from SL into Lion and try to run it? Does it work? :unsure:

Front Row.app doesn't contain anything crucial to Front Row, it's basically just a trigger to launch Front Row from the Dock. You would have to copy certain framework folders over from the System folder. Not sure it would work though, but it might.

My guess is that Front Row will be replaced by something else though that hasn't been implemented yet (hopefully).

Front Row.app doesn't contain anything crucial to Front Row, it's basically just a trigger to launch Front Row from the Dock. You would have to copy certain framework folders over from the System folder. Not sure it would work though, but it might.

My guess is that Front Row will be replaced by something else though that hasn't been implemented yet (hopefully).

I think they're just trying to really push Front Row now - at $99 it's quite marketable now. I could also see them porting that interface to the iPhone/iPad as an option when you plug it into a TV.

I think they're just trying to really push Front Row now - at $99 it's quite marketable now. I could also see them porting that interface to the iPhone/iPad as an option when you plug it into a TV.

Push Front Row ? You mean to a next level ?

I was thinking of ? having, you know, the same interface they put in their Apple TV. Why make a totally different interface for the same functionalities (or almost) when you can just stick this in directly. So your Mac becomes an Apple TV box completely. Could be cool.

Push Front Row ? You mean to a next level ?

I was thinking of ? having, you know, the same interface they put in their Apple TV. Why make a totally different interface for the same functionalities (or almost) when you can just stick this in directly. So your Mac becomes an Apple TV box completely. Could be cool.

Front Row will most likely be replaced by a full screen version of iTunes.

  • Like 2

Front Row will most likely be replaced by a full screen version of iTunes.

Yeah, that's what I'm thinking too. Lately new iTunes and Mac OS X releases aren't being released at the same time though.

I think they're just trying to really push Front Row now - at $99 it's quite marketable now. I could also see them porting that interface to the iPhone/iPad as an option when you plug it into a TV.

You mean Apple TV? $99 is pretty affordable, but there comes a point where I think I've spent enough money on Apple. Spending another $99 for what's essentially a streaming box only seems pointless.

  • 3 weeks later...

I just noticed Safari's Downloads window has been completely replaced by the new toolbar button. If you don't have the Downloads toolbar button added to the toolbar it will temporarily appear there.

For some reason I can't find drag lock anymore either in the Magic Trackpad preferences. Just three finger drag. :/ Can't stand it!

It won't appear on Software Update, only in the App Store. The only builds to show up via Software Update where the ones that went atop DP3, IIRC.

You could go from DP2 to DP3 using software update but I really doubt you'll be able to go to DP4 using the same method. Just use the AppStore it takes less than an hour

anyone else having problems with launchpad? some of the folders stutter when opening them, mainly the utility folder and also my icons have all disappeared for a load of the apps in launchpad.

im running developer preview 4, also does anyone know of an usenet app to download nzbs that works with lion? sabnzbd doesn't seem to work at the moment.

Just a quick question because I've had a mac less than a year and never had to use time machine yet (touch wood).

If I completely wipe my hard drive, install lion and restore from time machine, will I have issues if I then do a clean install of Leopard (i.e. does time machine not like going backwards OS versions)? Or are there any downsides to doing this at all other than the obvious time it will take to copy data back from time machine?

I've currently got it installed on a separate partition but it's got the the point where I am fancying it as my main OS, until we get the GM, but don't fancy losing all my data/having a nightmare with time machine

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I like the show more options. The only problem with it is that it's not always in a consistent spot in the menu. If the copy/paste/cut, happens to show on top, then more option is the last in the menu. But if copy/paste/cut happens to show on the bottom, then more options is before the copy/paste/cut. But I do like the more options because it hides the stuff that I rarely use. But I would like to choose what it is or isn't hiding. That would make it better.
    • I wonder if "put it back the way it was for decades" ever crossed their minds? 🤣
    • Rescind the stupid "Show more options" in context menus and just give us the full menu instead of adding more steps to get to what we want. The "simpler by default" makes me think they'll go in the opposite direction. Every context menu should have a configure button so you can pick and choose what options should be shown, I know you can do that with some registry fu but that shouldn't be required.
    • This is why competition must exist. Finally, pressure is mounting on Microsoft to move in the right direction.
    • Microsoft is making Windows 11's context menus faster, simpler, and configurable by Taras Buria Five years ago, Windows 11 introduced redesigned context menus, offering users a simpler, more modern design. However, customers quickly discovered that the new menus leave a lot to be desired. Many are unhappy with performance (they are really slow), while others dislike the double-layed design, where many options are hidden behind the "Show more options" button. In addition, over the years, menus became cluttered and overloaded. While Microsoft has already fixed plenty of pain points across Windows 11, context menus remain mostly unchanged. Fortunately, Microsoft is finally listening. Marcus Ash, Design and Research Lead for Windows at Microsoft, responded to a tweet on X, confirming that the company is working on fixing Windows 11's context menus. Reworked context menus are supposed to be faster, simpler by default, and "configurable to what you use most." What the latter means is unknown, just like whether Microsoft plans to keep the classic menu alongside the modern one, but according to Marcus, the wait should finally be over soon, as he promised to "share our approach soon." Improved context menus will most likely appear first in Windows 11 preview builds in the Experimental Channel. While we wait for Microsoft to release them, you can try fixing context menus on your PC with a simple tool called Windows 11 Context Menu Manager. It lets you disable entries you do not need, not only cleaning up context menus, but also making them significantly faster. Microsoft has already improved Windows 11's Start menu and taskbar, so hopefully it will address user criticism of the context menu as well. Stay tuned for new Windows 11 preview builds, which usually arrive every Friday.
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!