Feature request: better graphic acceleration in OSX guests under VMware Fusion

It is currently not possible to run standard Mac applications (such as iMovie, iDVD) on an OS X guest under VMware Fusion, due to the lack of graphic accleration.
Therefore I would like to post the following feature request:
please add support for Quartz Extreme / Core Image graphic acceleration in OS X guests under VMware Fusion.
Thank you!
magoo2

It is currently not possible to run standard Mac applications (such as iMovie, iDVD) on an OS X guest under VMware Fusion, due to the lack of graphic accleration.
Therefore I would like to post the following feature request:
please add support for Quartz Extreme / Core Image graphic acceleration in OS X guests under VMware Fusion.
Thank you!
magoo2

Similar Messages

  • Feature request: Better handling of accents

    Hi everyone,
    Since the "Provide iTunes feedback" menu item in iTunes itself only allows you to request music from the iTMS, I'm going to post my feature request for iTunes here, and hope that Apple picks up on it.
    For most of the English-speaking world, accented characters (e.g.: é, à, â, ö, etc...) are never used, but for someone like me who speaks French or someone who has international music, it's an important part of using your computer.
    So, here are two suggestions on how iTunes could handle accented characters more gracefully:
    1. Don't be so aggressive in the auto-complete behaviour! iTunes will routinely disregard capitalisation and accents in order to "fuzzy-match" the auto-complete.
    For instance, suppose I have an artist in my library named "Stephanie McKay", and I want to add another artist named "Stéphane Pompougnac". Here is how the auto-complete would look at six different stages (iTunes' suggestions are in square brakets):
    1. St[ephanie McKay]
    2. Ste[phanie McKay] iTunes replaces the é I just typed with a normal, unaccented e
    3. Stephan[ie McKay]
    4. Stephane iTunes doesn't have any suggestions to make at this point
    5. Stephane Pompougnac I've typed in the complete name, and now I have to return to put the accent on the first e
    6. Stéphane Pompougnac
    In this case, the 'é' should've stuck as of step 2 and iTunes should've not had any suggestions to make since nothing else in my library starts with 'Sté'.
    2. As far as searches go, the same is partially true, but with one caveat. If I'm searching for "Stéph", I should only get one result back, "Stéphane Pompougnac".
    On the other hand, if I'm searching for "Steph", I think there's a possibility that I was too lazy to type the accent or I didn't know if/where there was an accent, and so I should get both results back: "Stéphane Pompougnac" and "Stephanie McKay".
    The same is true of other accented characters (é, à, ö, ô, and even ç). I don't know how languages other than French and Spanish deal with characters that look alike (e.g. ø and o) or that represent the same thing, but if there is a relationship, I suppose the same behaviour should apply there.
    Cheers,
    - tonyboy

    Hi Brad,
    Thanks a lot for pointing this out. We have verified this. We are looking into this issue and would try to incorporate the fix in future releases.
    Regards
    Utsav

  • Feature Request - better croping, focus patterns,focal length selections?

    Tool specific Keyboard shortcuts:  It would be helpful to have popup clues about keyboard shortcuts.  For example, when using the crop tool,  it is not obvious that typing an "X" will change the crop tool from a portrait to landscape mode or repeatedly pressing "O" will cycle through a number of grids.  (Thank you Matt!)
    Crop at other than "Fit" setting:  Other crop tool request - allow crop to work on image at settings other than "fit"  I may be able to get a more accurate crop at 1:2, etc.  Otherwise I have to crop an image roughly, make a virtual copy and then crop again.  Is there a better way to do this?
    Show Focus Points on request:  If you shoot wildlife with a long lens, a slight error in focus can ruin the shot.  I review my bad shots to determine patterns of error in focusing.  It would be helpful to see the focus points that were used in Lightroom, (e.g. killer whales move differently than an egret....)  I assume this is stored in the metadata.  I'd love to be able to do this in Lightroom.
    Add Focal Length to filterable metadata fields:  It would help to be able to see the various focal lengths used during a shoot, just like you can look at apertures (i.e.  select folder for shoot, turn on filters, select aperture in the metadata and wallah!  you can see the distribution of apertures used during a shoot.)  This reminds you to mix it up and/or helps with lens selection.  Is there a way to do this now? 
    My apologies if these features are available and I just haven't found them yet.
    -TAB, a lightroom fan
    P.S. Thank you for the wonderful new features.  I can't wait to convert my existing catalogs.  I love the new import dialog.  Now I can organize my backup copy in a logical fashion.  When I'm in the field on a multi-day shoot, I don't want to risk reorganizing the backup.  Now I don't need to.  Enough has been said about noise reduction and better rendition.  Thank you!!!

    There is a corresponding idea at the feedback forum: http://feedback.photoshop.com/photoshop_family/topics/add_image_direction_in_map_module
    Anyone who wants this feature should also vote over there...
    BTW: +1
    Edit: P.S. I think it is generally a better idea to post feature wishes in the feedback forum (or comment on existing ones there) because it's regularly monitored by Adobe employees, while that is not necessarily the case for the user-to-user-forum here.

  • Feature request: better keyword management tool

    I'm re-organizing my keywords and I think that LR needs some work in keyword management and DAM features.
    I miss something like separate keyword management tool which would have two keyword lists, which would work a bit like spatial file management in Os X finder.
    Easily manage keyword hierarchy. For example: browse list and and be able to easily select keywords (now it's OK) and drag and drop them to under a new keyword (almost ok, but sometimes cumbersome, if one wants to move keyword which is/are at the bottom of the long keyword list to keyword which is at the top of the list).

    KKuja wrote:
     ...if one wants to move keyword which is/are at the bottom of the long keyword list to keyword which is at the top of the list.
    Dang near impossible once you have a lot of keywords. A work-around for me has been to filter keywords first to reduce the number of keywords in the list, then do the drag 'n drop. At a minimum, a change to scroll the list when you're searching for a drop target at a variable rate that depends on mouse position, or even something simple like slowing it down when the alt key is pressed.
    +1 vote - better keyword management.
    Something else that may help you in the mean time: KeywordConsolidator.
    Rob

  • Feature request: Better tool for organizing image files

    Hi all,
    I'm considering rearranging the directory structure of my photo library completely (for a number of reasons: new cameras, a new variety of tools on new PCs).
    I would like to reorganize my photos into a year\month directory structure and that will basically spread all my image files into new locations.
    I have searched quite a bit and the advices I have seen don't seem to work:
    (1) Moving the files outside LR is fairly easy (using exiftool) but I cannot make LR link to the files automatically in their new locations. And doing it manually with "Locate file" or "Find missing folder" is not practical due to the large number of files and large number of new locations.
    (2) Moving the files with LR tools is also not practical: Manually dragging the photos into the new directory structure will take forever, and the only automatic rename feature I know of is "Rename Files ..." cannot move the photos into new directories (it can, however, assign names from the file dates and other metadata).
    Now my feature suggestion: Either make it possible for LR to automatically relink files that have been scattered into a new directory structure or - better yet - make it possible for LR to perform such auto-organize operations.
    My mp3 manager (MediaMonkey) is a good example to follow: It can organize (move or copy) any number of music files into any directory structure built from the audio file's metadata (such as my standard audio directory structure: Music\<Artist>\<Album>\<Track#:2> - <Title>).
    Interestingly, the LR "Rename file" function can almost do it already; it just cannot move the file into a new directory.
    Or can this be done in a way I haven't discovered?

    Sorry if I might be stating the obvious (but at least I was such a *dummy* once that I needed this explicitely):
    In order to move the sequence of images per drag&drop in grid view you need to
    Put the sort order in the bottom toolbar to "user order" (toggle visibility with letter T if not displayed)
    Grab an image from within its thumbnail, not from its border-cell.
    When you move around you see a vertical black thick line wandering in between images where you would be able to drop it
    Put the images first into a collection in case they should be spread across multiple folders.
    This is the reason why most often from a filter result you cannot re-arrange.
    Still sometimes it does not work as I want, but can *be persuaded*, i.e. I repeat the same trial after first moving to another collection, then return back. I can't nail it down sufficiently to file a bug.
    For an automated sorting according to filename (chosse that setting finally in toolbar) you could rename the photos in place, without exporting & re-importing. Just select them and hit <F2> to bring up the renaming dialog like possible during import.
    +1 vote from me, as I am neither satisfied with the responsiveness of moving folders within LR e.g. from laptop hard disk to NAS.
    Apart from that I try not to build much on my folder structure, just break them into manageable quantities and have a quick "diary-overview" by using naming convention "YYYY-MM-DD description of event" (pictures of up to 4 cameras go inside, unique filenames for Canons achieved by renaming during import). For all the rest I prefer to build (smart) collections.

  • Two feature requests (custom graphic placeholders & variables)

    After building several pages document templates, there are two features that would be a big help.
    First, I created some graphical text boxes similar to those used in many manuals. The color coded box contains placeholder text and an icon to indicate note type. It would be great if I could define and manage these similar to pages. Allow the user to insert a warning box, an informational note, etc. These items would be self contained graphics with placeholder text, etc. User inserts one, modifies the text and then moves it into place. Each template should support an unlimited number of these document specific graphical objects.
    Second, There needs to be a generalized variable scheme similar to the new address book feature. If I insert a page type, I might want to carry the section title or other info as one or more variables so that they can appear in later headers, footnotes, etc. for that section. Using the Business:Meeting template as an example. If I add a agenda page, it would be nice to automatically carry the meeting date and topic in the header of each additional page of agenda. Currently, the user would have to type/format info in page 1 of agenda and remember to do it in the header of agenda page 2 if the agenda failed to fit on a single page. If this info was in variables, I could define/format it for use the the header except for the first page so that it would automatically appear if the agenda ran long.
    Our company has begun using Pages '06 for documents that must be repeatedly repurposed for customer email, web page spec sheets, quotes, etc. since the templates can simply be saved as pages documents on the Admin. Assist.'s machine and stored as PDFs in a public area. The admin can easily keep both locations current as specs change, etc.

    Hello delemex,
    welcome to the Pages Discussions. But if you want to reach the developers you should send them a notice about your thoughts. Here we are all users and we try to help each other to solve problems (alright, sometimes we discuss features, too).
    Follow this link http://www.apple.com/feedback/pages.html to send a feedback.
    Edit: And if you don't like mine, follow Peggys link
    Frank.

  • Feature Request: Better dimensional meta data displayed

    Aside from every other problem with how Bridge lets the user display, sort and interact with meta data (aside from the actual metadata palette), it would be way more useful to have the Dimension meta data displayed under an image shown in 'real world' dimensions.
    For example: I'm looking at my 'final images' that have been converted to CMYK, and sized for delivery. At this point Pixel Dimensions are pretty useless. What I really want to do is quickly scan my images, seeing Inches (or CM) with a PPI. My clients never ask for pixel dimensions (unless we are talking about the web, which we aren't) - they ask for 8.76" x 5.34" at 266ppi. It would just be nice to use bridge to double check the image sizes before delivery.
    thks
    andy

    Thanks for you feedback. You wish has been granted (dimensions can now be displayed in pixels, inches or centimeters. Go to Preferences > Thumbnails to select which dimension to display below the thumbnail, or Preferences > Metadata to customize the metadata pane). Check out the free beta of Bridge CS3 (http://labs.adobe.com/technologies/photoshopcs3/)
    Cheers,
    Arno.
    Bridge Engineering Manager, Adobe.

  • Feature Request: Better format options Please!

    I've been using Adobe Story recently and think it's a great, competitive product that definitely rivals other products!
    However, I do think there need to be a few more output options to increase compatibility with writers and producers who may not necessarily be using the latest software. In particular, .rtf and .fdr (Final Draft 7 or older) formats are not given as options to export and this would be very handy as I know plenty of writers who have not upgraded to Final Draft 8 and therefore cannot read the new .fdx extension on files.
    Adding these two little things shouldn't be at all difficult and would allow much greater flexibility for users of Adobe Story to share material out without the need of the other party having to reformat things on their end.
    Hopefully I'm not the only one looking for this feature update?

    Hi Deepak
    Thanks for your response. Don't take this the wrong way and please don't feel like I'm shooting the messenger here, but honestly speaking I think rtf *and* fdr format compatibility should be in your frontlog considering you are making a version 1 product that's trying to compete or at least compliment industry standard tools!
    Having only fdx compatibility is like Office 2007/2010 only having .docx with no backwards compatibility for legacy formats - it renders the tool useless in the eyes of many potential customers. It great to push new and more open formatting standards but there must, must, must be legacy support too - I mean you already support import of rtf and fdr so it's nuts that it doesn't go out that way too!
    I have found that having .txt and .pdf as a bridge for the older software tends to be an inefficient workaround. There are always occasional formatting errors that crop up due to the use of some type of special character that isn't translated properly in the conversion and therefore there is always a need to spend an additional 15-20 minutes re-checking entire scripts to make sure there are no problems before sharing the material to a colleague or client who either cannot afford to or hasn't bothered to upgrade to Final Draft 8 (or Adobe Story ).
    That's just my two cents but I'm sure that many people would agree with me that this small update should be a priority to make AS (sorry, I've gone an abbreviated another one of your products - doh!) a more appealing alternative to the tools people may have been used to in the past.
    Hope you take this pledge into serious consideration for your next upcoming update!
    Thanks,
    Kaush

  • Feature request: better tools for commenting and editing text

    We currently use a comments-enabled Acrobat workflow with InDesign to track changes to our large catalog project. Was hoping to move our team over to CS Live, but currently the commenting tools are sub-par, and not accurate enough for extensive text editing. My request would be to imitate the text editing functionality of Acrobat:
    In CS Live online:
    - allow users to be able to copy selected text. (This is useful when a reviewer wants to be able to modify a sentence or paragraph. It's a headache now to have to retype the sentence prior to making modifications)
    - Ability to highlight text and hit "delete" to mark text as deleted, or highlight and type over to indicate replaced text
    - Ability to click to insert text, and have the comment appear with the inserted text designation (little blue carat like in Acrobat)
    - ability to highlight a section of text
    In InDesign:
    - ability to copy the text in a comment and NOT copy all the other extraneous meta data. (Currently, if you click "copy text", it will copy the comment along with all the details about the comment. For example, "- Amy Stewart [10.06.11 at 12:56 PM]"
    - ability to see in InDesign the EXACT part of the text that needs to be modified. Right now, the red box outlines the general area. The CS Review panel shows a tiny thumbnail with black highlight over the area of text that needs to be changed, but unfortunately, there's no way to zoom in on it, so you're stuck having to toggle between InDesign and the online review, where it's possible to zoom. (This diminishes the utility of the CS Review panel.)
    If you were able to incoroprate all the commenting functionality of Acrobat, I think you'll have a winner. But right now, we're going to have to stick with Acrobat as it's the only way to easily modify text.

    Sorry if I might be stating the obvious (but at least I was such a *dummy* once that I needed this explicitely):
    In order to move the sequence of images per drag&drop in grid view you need to
    Put the sort order in the bottom toolbar to "user order" (toggle visibility with letter T if not displayed)
    Grab an image from within its thumbnail, not from its border-cell.
    When you move around you see a vertical black thick line wandering in between images where you would be able to drop it
    Put the images first into a collection in case they should be spread across multiple folders.
    This is the reason why most often from a filter result you cannot re-arrange.
    Still sometimes it does not work as I want, but can *be persuaded*, i.e. I repeat the same trial after first moving to another collection, then return back. I can't nail it down sufficiently to file a bug.
    For an automated sorting according to filename (chosse that setting finally in toolbar) you could rename the photos in place, without exporting & re-importing. Just select them and hit <F2> to bring up the renaming dialog like possible during import.
    +1 vote from me, as I am neither satisfied with the responsiveness of moving folders within LR e.g. from laptop hard disk to NAS.
    Apart from that I try not to build much on my folder structure, just break them into manageable quantities and have a quick "diary-overview" by using naming convention "YYYY-MM-DD description of event" (pictures of up to 4 cameras go inside, unique filenames for Canons achieved by renaming during import). For all the rest I prefer to build (smart) collections.

  • [Feature Request] Better support for new buttons in JUNavigationBar

    In my project I use a home made sub-class of JUNavigationBar, which contains some new functionality apart from a new button as well. This button allows me to refresh the currently selected row.
    However, since I added this button though a simple this.add(), some of the functionality in JUNavigationBar may get confused.
    For example, when I have removed some of the standard buttons but left my own button in place (setHasXXX()), the component index (calculated in JToolBar) and the array index for the buttons in JUNavigationBar may not match. This occasionally causes an ArrayIndexOutOfBoundsException.
    In short, what I'm asking for, is a better way to manage buttons on JUNavigationBar. Even making the array of buttons and related methods and such protected in stead of private (so that my sub-class could handle it) would be a good start.

    Hi Arno,
    I had a similar issue with trying to create a Nav bar with dynamic content. My solution was to leave all the standard buttons in place and to use setVisible(x) to make them appear or not as required.
    BTW have you noticed that rollover behaviour isn't consistant ie works for FIRST/LAST etc but not for FIND/QUERY.
    Regards
    Andy

  • Feature Request - Better Multiple Monitor Support

    Lightroom's support for a second display has definitely helped my  workflow. I hope the team will consider adding more flexible multiple  monitor support in version 4. Here's why.
    I've recently  experimented with running one of my three screens in portrait mode. When  this screen hosts Lightroom's secondary display window in Loupe view,  my verticals finally get equal real estate for editing. While I've not  done hard statistics on my library, I know more than 50% of my imagery  is in portrait orientation.
    I'd like to see LR V4 support three or more screens so I could set up as follow:
    Screen 1 - main lightroom interface, would not need to be calibrated, for controls and navigation
    Screen  2 - Portrait orientation, loupe view - this would be a calibrated  display, all develop changes to verticals would be judged on this screen
    Screen  3 - Landscape orientation, loupe view - another calibrated display, all  develop changes to horizontals would be judged on this screen
    If  Adobe could make the app intelligent enough to route the image to the  correct screen based on orientation (recognizing and respecting cropping  that could change orientation) my edit sessions would certainly speed  up and I could maximize the productivity of multiple screens.
    I'd  be happy with this, but I'm also stymied by the need to switch back to  Library mode to tag images when my primary workflow has me in develop.  Ultimately everything depends on the quality of the image. Before I  invest in image-specific meta data, I have to process or at least  "test-process" an image. IMO the Quick Develop panel is useless, once  you become accustomed to the granular control of the develop sliders, it  just doesn't cut it.
    In the three monitor setup I described  above I'd love to be able to configure screen 1, with a combination of  panels from Library and Develop, so I could stay "develop centric" with  immediate access to keywording and meta. The two additional screens  would intelligently handle image display.
    I think this might  speed my workflow by 33% and having just returned from a Tour de France  project that generated 23,000 images I need all the productivity help I can  get.

    VeloDramatic wrote:
    Thanks for all those votes Rob. Now we just need to get the other 999,999 on board.
    Actually, this topic has come up a lot on this forum. At this point, I think we just need to get Adobe on board.
    VeloDramatic wrote:
     There may be another thread for this one additional thought. If Adobe does improve multiple monitor support, we should be able to optimize our previews for those screens. Even after prerendering 1:1 previews there are issues with DEVELOP doing its own thing (I believe) each time a new image is loaded. I make extensive use of the PREVIOUS button moving through my shoots and there's always a lag of one or two seconds while the develop preview loads before the button is active. In a desktop environment where multiple screens allow landscape and portrait images to be displayed full screen I'd argue that 100% of the host screen resolution would be the ideal preview. Hope that made sense.
    Yes, faster switching would be nice. I'm not sure what that would take. As it stands, there's like "9" previews generated when you do 1:1s - 100% down to tiny thumbnails. Still, one at exact monitor size that does not need to be resized at all does seem like it would be the fastest - I'm a bit on a limb though at this point.
    Rob

  • Feature request: Better keywording options

    There appears to be no improvements in keywording otpions in LR4b.
    How about:
    Larger panels of suggested keywords. (could be configuarable in options, like the number of recent files option in PS)
    Larger numbers of keywords in a set.
    Buttons to apply a complete set with one click.
    Put the keywording tools,( ie the same panels as in library module),  in the import dialogue.

    Hi Deepak
    Thanks for your response. Don't take this the wrong way and please don't feel like I'm shooting the messenger here, but honestly speaking I think rtf *and* fdr format compatibility should be in your frontlog considering you are making a version 1 product that's trying to compete or at least compliment industry standard tools!
    Having only fdx compatibility is like Office 2007/2010 only having .docx with no backwards compatibility for legacy formats - it renders the tool useless in the eyes of many potential customers. It great to push new and more open formatting standards but there must, must, must be legacy support too - I mean you already support import of rtf and fdr so it's nuts that it doesn't go out that way too!
    I have found that having .txt and .pdf as a bridge for the older software tends to be an inefficient workaround. There are always occasional formatting errors that crop up due to the use of some type of special character that isn't translated properly in the conversion and therefore there is always a need to spend an additional 15-20 minutes re-checking entire scripts to make sure there are no problems before sharing the material to a colleague or client who either cannot afford to or hasn't bothered to upgrade to Final Draft 8 (or Adobe Story ).
    That's just my two cents but I'm sure that many people would agree with me that this small update should be a priority to make AS (sorry, I've gone an abbreviated another one of your products - doh!) a more appealing alternative to the tools people may have been used to in the past.
    Hope you take this pledge into serious consideration for your next upcoming update!
    Thanks,
    Kaush

  • Feature request: horizontal mouse scroll

    Hi,
    I would like to submit the following feature request:
    please improve the emulated mouse in Windows guests in VMware Fusion so that it can handle horizontal scrolling made available by mice with a "tilt wheel" (such as those from Logitech, Microsoft and the Apple magic mouse). Currently, it only supports vertical scrolling.
    Thank you!
    magoo2

    Hi,
    Send feedback to Apple here:
    Safari menu > Report Bugs to Apple...
    This forum is just for users to help other users, so the powers that be won't necessarily see your idea

  • Feature requests for LR4 beta from a wedding photographer

    I would love to see some more auto white balance algorithms.  There are many other algorithms that do an outstanding job that could be implemented to speed up workflow for busy photographers for when the lightroom autobalance doesn't work.  Some of these include:  i2e (colour science), perfectly clear, and xe847.
    These 3 algorithms also apply an auto-toning feature which, when the Lightroom version doesn't work, these might give excellent results quickly.  Photoperfect is a program that implements these 3 technologies into its interface and is excellent for quickly tweaking jpegs and tiffs.  I would love to see this same capability married to Lightroom's excellent raw conversion engine and outstanding new highlight and shadow sliders.
    A skin-tone white balance would be most welcome. Silkypix has this feature.  When there is no neutral coloured object, you can click on a skin-tone and this will often white balance the image correctly.
    More profiles would be welcome.  To use Silkypix 5 Pro as an example again, it has 6 portrait profiles--these are most useful for achieving the perfect look for your photograph.  Some are good for single light sources, while others excel at providing pleasing colour under mixed light sources.
    Sliders to fine tune noise reduction based on tone (ie. shadow, midtone, and highlight) would truly make Lightroom's noise reduction the gold standard.

    As these requests may not make the final release, and we wouldn't want the request to get lost in beta land, might I suggest adding it as a suggestion on the Feature Request forum http://feedback.photoshop.com/photoshop_family where it can easily be tracked?  If you post the link to your request here, others can also vote on your request.  You may even find a few of them already requested over there, so you could add your vote.

  • Better system for collecting feature requests

    See how feature requests are handled for Gallery:
    http://gallery.menalto.com/sfvote

    Roadmap questions cannot be addressed at CSC, you need to direct this to your account team.
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

Maybe you are looking for