Feature request: make enhancer more silent

It would be nice if the enhancer only reported (or had an option to only
report) the classes actually enhanced.
Currently (as of 2.2.6) it displays:
Enhancing "class x"...
Type "x" is already PersistenceCapable; skipping.
Cheers,
Sebastien

I second that.
Paul
Vauclair Sebastien wrote:
It would be nice if the enhancer only reported (or had an option to only
report) the classes actually enhanced.
Currently (as of 2.2.6) it displays:
Enhancing "class x"...
Type "x" is already PersistenceCapable; skipping.
Cheers,
Sebastien

Similar Messages

Feature Request: Make a Setting Option for Export - Media - What to Render

As I just changed after many years with Premiere Elements to Pro, I certainly find many things just anconversant.
But there's one thing I really can't take: When I'm trying to render a project, there's a small selection list near the bottom of the "Export Media" window saying "export area". Here I can choose between "complete sequence", "work area", "sequence in/out" and "defined by user". This option jumps always back to "work area"!
That's at least for me very unconveniant, because in 99+ % of my renderings, I need "complete sequence". Normally the software remembers the last used setting, but not in this case. I can imagine that one can fight about what's the best default setting: I Guess everyone is using Premiere differently. So in my opinion a predefined setting option would solve best for all: Just add one mor setting in the Presets section, maybe in "General" or make a new rubric "Export" or something. Just a place where everyone can predefine which setting for the export media area option he likes.
No big deal, just one more presettings option!
I hope I could make myself clear what I'm meaning
Thanks in advance!

Hi Lutzz,
When I'm trying to render a project, there's a small selection list near the bottom of the "Export Media" window saying "export area". Here I can choose between "complete sequence", "work area", "sequence in/out" and "defined by user". This option jumps always back to "work area"!
That's at least for me very unconveniant, because in 99+ % of my renderings, I need "complete sequence".
You can create a feature request here: http://adobe.ly/feature_request
Thanks,
Kevin

Feature request: make podcast "Keep" preferences specific to each podcast

I subscribe to many different podcasts of different types for various reasons. With some podcasts I want to retain all episodes in an archive. With others I want to delete them as soon as I have listened to them. With others I might want to keep them for a week or month and then delete them even if I have not gotten around to listening to them. It would be very nice to be able to set a default preference for how long to keep podcasts in the iTunes preferences, just as can be done now, but to be able to override that default preference on a podcast by podcast basis. Please give us this ability to make podcast-specific decisions on how long to keep individual episodes. Thank you for considering this request.

You can send feedback/feature requests directly to Apple at this link: Apple Product Feedback

FEATURE REQUEST: make swipe-down Notifications bar disable-able

I use the iPad as a drawing tablet every day, using Brushes, ArtRage, and other drawing apps.
It's wonderful and I am delighted to be able to do this . . . EXCEPT WHEN I DRAW A STROKE DOWN FROM THE TOP OF THE SCREEN.
The introduction of the new pull-down Notifications drawer has led to loud cursing and a strong desire to break things, for me. When one is drawing, one is not in a state in which one wishes to glance at what the next day's schedule is at. Furthermore, the active area of the pull-down also 'catches' the drawing input, so the stroke which is misdirected into the Notification dialog is lost work, and subsequent rapid stokes, up to the threshold of my reaction time, also do not register.
I must then dismiss the godforsaken irritating dialog in order to continue drawing. It is the most incredibly irritating interaction I have ever experienced on an Apple product.
Please permit the dialog to be disabled either user-globally or on a per-app basis as a user-configurable setting.

even with all notifications turned off the drawer remains active. there's no way to disable it.
while this may be a user to user forum apple people do contribute. I did file this as a feature request but wanted it to be visible and searchable.

Feature request: Support for more than 2 monitors

I currently use an external monitor for my critical editing/evaluation as my iMac display doesn't reproduce reds very well. I understand newer iMacs can support 2 external displays, obviously desktop machines can support as many displays as there are open slots for video cards.
While editing a photo shot in portrait on a monitor set for landscape is not a problem, it would <really> be cool to have two external color-accurate monitors for developing/loupe views, one oriented in portrait, one in landscape, with the third (iMac in this case) showing the develop controls. Even if the two external monitors showed the same image, one would always be fullscreen in the correct orientation.
MacOS and Windows both give the user control over all the displays connected to a given system, so driving a portrait and a landscape monitor simultaneously shouldn't be a problem from an OS/hardware standpoint.
Is this something that can be rolled into LR4?
Respectfully,
Andre

I use 3 or 4 monitors too, so that's one I'd like to see too. We wouldn't want the request to get lost in beta land, so might I suggest adding the request to 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.

Feature Request: Make RECENTS better with two more drill down options

Hi everyone!
I love my iPhone but - as with everything - one can make things get even better... Not sure where to post so I try here. Would love to hear if you feel the same need:
I realize that RECENTS within the phone application could be improved quite a bit by adding two simple buttons at the top.
Right now there is "ALL" and "MISSED"... being able to drill down the MISSED calls is great, but many times I would like to be able to drill down:
* outgoing calls (aka those placed by me via iPhone)
* incoming calls (aka those that I received on my iPhone)
Would love to hear what others think about that. If we there will be many replies chances are good that Apple will fix this with a software update. It should be very little work on Apple's side.
Greetings!

I agree this feature would be most useful: most other phones incorporate it, and it would probably not be too difficult to add it to the iPhone? I expect most will agree with you, but this type of feedback should be sent directly to Apple:
http://www.apple.com/feedback/iphone.html

Feature Request to enhance Weblogic Tech Support

Hi,
I will try to express my idea in "draft" form. I think weblogic architects
can enhance the ideas to hashout all the necessary details.
It will be very good to have following environment variables in
startWeblogic.cmd / startWeblogic.sh files:
ENABLE_RECORDING=True/False
RECORDING_MODULES=JMS;RMI;EJB;ServletEngine;JSPEngine;...
RECORDING_OUTPUT_TYPE=Text/Binary
Through these variables developers can tell the system to record "important"
information necessary to capture the problem they are experiencing.
The output file (text or binary) can be sent to tech support to reduce
speculation and inhance correct analyzation of the issue at hand.
Each module can be peppered with log() statements that would check the
environment variable and spit-out "important" system status as the product
runs to encounter the problem at hand. Also it will be extremely easy to
capture the WLS version and service pack level, O/S details, JVM details
into the output file. This will greatly eliminate the obvious questions
like: what was the version of WLS? Did you apply SP4?, What was your
CLASSPATH? etc.,
Developers can use this feature to quickly capture important system state by
replaying the trouble scenario and send the output file for further
analysis.
This would reduce the total time necessary to debug the problem and also
improves the accuracy of the problem analysis.
I envison that WLS will continue to evolve to add more and more features.
So, A feature like this would greatly improve the assistance developers can
get from tech support teams.
If these properties can be changed at runtime through weblogic server
console, then it will be extremely helpful to debug production systems
without restarting them.
Also this feature would greatly distinguish the WLS product from competition
regards,
Satheesh Donthy

We have written a JSP that gathers this info from the log file and allows the
customers to email it to whomever or to save it to disk and mail it with their
own mailer as an attachment. So what we have here is functionally complete, but
we want you to test it and give us your feed back and let us know how we should
change it. It is a bit ugly because it has to support so many versions and
there have been API changes and we wanted to make it inclusive all in one file.
Very soon this will be pushed on to developer.bea.com and will also be included
with SP6
This works fine from 451 to 51 SP-3. This may not work with SP4 as they
are some problems with inner classes in SP4 which we are looking into it..
Your feedback will be highly appreciated.
PS: Courtesy of Mark Griffith.
kumar
Satheesh A Donthy wrote:
Hi,
I will try to express my idea in "draft" form. I think weblogic architects
can enhance the ideas to hashout all the necessary details.
It will be very good to have following environment variables in
startWeblogic.cmd / startWeblogic.sh files:
ENABLE_RECORDING=True/False
RECORDING_MODULES=JMS;RMI;EJB;ServletEngine;JSPEngine;...
RECORDING_OUTPUT_TYPE=Text/Binary
Through these variables developers can tell the system to record "important"
information necessary to capture the problem they are experiencing.
The output file (text or binary) can be sent to tech support to reduce
speculation and inhance correct analyzation of the issue at hand.
Each module can be peppered with log() statements that would check the
environment variable and spit-out "important" system status as the product
runs to encounter the problem at hand. Also it will be extremely easy to
capture the WLS version and service pack level, O/S details, JVM details
into the output file. This will greatly eliminate the obvious questions
like: what was the version of WLS? Did you apply SP4?, What was your
CLASSPATH? etc.,
Developers can use this feature to quickly capture important system state by
replaying the trouble scenario and send the output file for further
analysis.
This would reduce the total time necessary to debug the problem and also
improves the accuracy of the problem analysis.
I envison that WLS will continue to evolve to add more and more features.
So, A feature like this would greatly improve the assistance developers can
get from tech support teams.
If these properties can be changed at runtime through weblogic server
console, then it will be extremely helpful to debug production systems
without restarting them.
Also this feature would greatly distinguish the WLS product from competition
regards,
Satheesh Donthy[serversave.jsp]
[serverinfo.jsp]

Feature request: make the "transform" dialogs non-modal

Currently, the transformation dialogs accessible at Object>Transform are modal. I'm talking about "Move…", "Rotate…", "Reflect…", and so forth. These dialogs, when open, lock the user out of any interaction with the artboard other than the "preview" button, until the dialog is closed.
Even more problematically, they lock the scroll and zoom factor of the current user view, so that there's no way to inspect how a precise numeric adjustment affects a part of the layout outside the current window (or within the current window but very small inside it) without committing the change, inspecting it, and then later undoing if necessary. This creates cycles of tedious user adjustments (especially on small monitors) that really should be possible in one user step, by toggling the preview button on and off, and zooming/scrolling.
This is contrary to most modern UI design principles, which suggest avoiding modes unless they are truly and meaningfully necessary. I don't think this is one of those cases. Photoshop made dialogs for adjustment layers non-modal with CS4, and while there are issues with the newer interface (see John Nack's Configurator workaround), I think it's a win overall. Illustrator needs to catch up in this regard. I realize there is some pretty serious refactoring involved to do this, but it has to be do-able.
In the words of Larry Tesler's immortal Subaru license plate: "NO MODES"!

...make the "transform" dialogs non-modal...
What, and bring Illustrator out of the 1980s?! Are you mad, man?
Just so you know you're not alone; I've been complaining about AI's archaic dependency upon modal dialogs for many years.
...I'm fully aware of the Transform panel...observing that there's another way to do it...doesn't really address any of my points here...
But it's not "another way to do it," because the functionality is not the same. The modal dialogs include crucial functionality that cannot be done in the Transform palette. For example, moving something in terms of distance and direction (diagonally), instead of merely by lame X and Y factors. Or transforming about an off-object center of transformation, rather than merely by the 9-point proxy.
...the "preview" isn't updated on keyboard entry, and the "preview" checkbox need to be manually toggled on and off...
But the preview does refresh (and does not have to be toggled) in response to keyboard entry if that keyboard entry is by the arrow keys. For example: Select something, doubleClick the Scale tool, click your cursor in the Uniform value field, and tap the up/down arrow keys (or press and hold them). The value will increment and the preview will update with each key tap. (Be sure to teach that to your students.)
That does not, of course, negate the complaint, but it does ameleorate it somewhat. The increments are preset; there are no preference settings for them. (Don't even get me started on preferences that should be doc-specific settings, and vice-versa).
Nor does the valid point that problematic dialogs abound beyond just those associated with the transform tools, but I do agree with it. For just one of many examples, it's nothing short of idiotic that the Scale fields of Transform Each do not have a uniform scaling lock, and that only percentage fields are provided and no explicit dimension fields. Illustrator is quite saturated with such inconsistencies and half-baked implementations.
But...you're often arguing with the emotionally attached Illustrator devoted here. So I wouldn't recommend holding your breath. It would probably be more effective teaching Illustrator's shortcomings to your beginning students. Probably one of the easiest ways to explain the problem of modal dialogs is to point out that you can't change the current selection with the dialog open.
JET

Feature Request UI builder: More use of Ctrl + ... similar to LabVIEW

Would like to see more use of the Control + Key for common features that are in LabVIEW. Run for example is Ctrl + R

I agree this option would be great to have built in automatically. It might also be nice to allow auto-indixing of 2d (or more) arrays going into for loops where it will iterate through all dimensions an grab the (i,j) single elements and add an i and j index inside the loop, instead of nesting loops inside of each other. I guess these features cater to the power users who want to save any amount of coding possible.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Feature Request - Make it run without crashing

I have two windows computers running XP SP2. Bridge used to run fine on both and now will not keep running on either. It opens, sits there and will see pictures on my C drive, but the a few seconds after I select another internal drive, it crashes with the wonderful "Bridge has had to close" drop down.
I have reset preferences until I am blue in the face but nothing ever changes. I don't know why this has gone on for at least a year and yet I see no fixes for it from adobe. I would be happy to be a guinie pig for any attempts to patch-correct this seemingly widespread problem.

Check the RAW and normal cache directories for space allocated and space used. Make sure you have no more than 80% of the space filled up. Give it room to work freely.

Feature Request: Make iBooks' dictionary accessible in Safari too

Make it possible to tap a word on a Web page opened inside Safari and then select dictionary to lookup its meaning.

This is a feature to implement in the future, please communicate that through the feedback channel:
http://www.apple.com/feedback/ipad.html
enjoy your magic machine

Tethered Capture feature request - make a 2nd copy

Make a 2nd copy feature is available during import of images, so why not whilst shooting tethered. Would love to see that feature. Please please please consider adding.

Short answer: No. That is the way it is.
Why? The Make Second Copy during Import is designed to be a backup of your memory card processes-not a back up of your files as you store them on disk. It is intended to be a transient copy that allows you an immediate backup until such time as a File System Level backup can be performed, allowing you to have two copies so that you can reformat your memory cards.
I agree it would be nice if the folder storage strategy was duplicated for the backup as it is created for the import but that is not something you can set the program to do currently. I remember it behaving differently versions ago but do not recall exactly how it used to work.

Feature Request - Make Outgoing Message in Garage Band

I want to be able to pre-record an outgoing message in Garage Band and then upload it to the phone to use as my custom outgoing message.
That would be cool and sound good.

That's probably information you should get from the manufacturer of your telephone.

Feature Request: Make SDK-Min & SDK-Ver Available

'Twould be awesome to be able to build common/shared/library code that can auto-detect the minimum and "maximum" SDK that a plugin is targeted for in order to adapt behavior or throw proper errors...
Tnks,
R

Yeah.
One of my favorite uses is for displaying Lr compatibility.
I'm taking advantage of the fact that Lr does not care a whit what you set LrSdkVersion to, and using it to indicate maximum compatible version for display in info-provider. Thus, if my plugins don't say: "Compatible with Lr3", then even though they load, and may even run somewhat, you can be sure I have not tested and certified them for Lr3... (and vice versa...)
Now that I think about it, adding "Mac support level" to the info.lua return table is not a bad idea - for display in info-provider.
PS - I suppose we should be adding some of this knowlege to the new repository...
Rob

Creative Cloud Feature Request: make it easier to edit credit card info

It is painfully difficult to find the area where my credit card information can be changed.
This is something that isn't done often so it's hard to remember what was done the last time.
I would love to see it show up under My Adobe or My Information. This would be much
easier for everyone... I just know it.
Thank you for your consideration and for your wonderful products.

Hi cagiali,
Please refer the kb: http://helpx.adobe.com/x-productkb/policy-pricing/membership-subscription-troubleshooting- creative-cloud.html and contact our chat support in case of further issues.
Regards,
Romit Sinha

Feature request: make enhancer more silent

Similar Messages

Maybe you are looking for