Skip to main content

Filter by idea status

10000+ Ideas

Support Windows standard double-click on title bar to maximize/restore windowOpen for Voting

Attn: Photoshop Product Management Team345 Park AvenueSan Jose, CA 95110-2704Submitted Online Via: Adobe Community Forums / WishformSubject: Feature Request: Support Windows standard double-click on title bar to maximize/restore windowAdobe Product Team,To improve workspace window management in Photoshop to better align with native Windows operating system behaviors, always show Windows controls anytime the titlebar is visible.Currently, double-clicking the title bar in Photoshop does not consistently maximize or restore the window down to its previous size, which contradicts standard Windows UX guidelines.This behavior is most troublesome when Photoshop enters a state where the title bar remains fully visible, but the three standard Windows control buttons (Minimize, Maximize, and Close) completely disappear from the top-right corner. When this glitch or view mode occurs, users are trapped in a borderless state with no clear visual way to scale down or close the application window. If double-clicking the title bar worked natively to toggle window sizes, users could instantly restore their screen layout without needing to guess keyboard shortcuts.Implementing this standard behavior would make the interface much more intuitive for Windows users, improving workflow efficiency and reducing confusion when managing multiple application windows.Thank you for considering this enhancement.

健太郎5EDAParticipant

Allow UXP extensions to read text from timeline clips and write it into MOGRTs, enabling automated subtitle and title styling workflows.Open for Voting

Premiere Pro UXP API: Add Read/Write Access to Text and MOGRT PropertiesI would like to request expanded text and MOGRT property access in the Premiere Pro UXP API.Current ProblemI am developing a Premiere Pro UXP extension to automate repetitive editing tasks, especially subtitle and title workflows.Currently, UXP provides useful capabilities for timeline automation, MOGRT insertion, effects, and other editing operations.However, access to text and graphic properties is still limited.This makes it difficult to build a complete automated workflow for text-based editing.What I Would Like to BuildA typical workflow would be:Existing text/graphic clip"Hello World"↓Read the text through the UXP API"Hello World"↓Insert a predefined MOGRT↓Write the retrieved text into the MOGRT↓Result:The original text is automatically converted into a designed MOGRT while preserving its text content.This would make it possible to automatically convert large numbers of transcript-generated titles or subtitles into professionally designed graphics.Requested API CapabilitiesI would like the UXP API to support: Reading text from text/graphic clips on the timeline Modifying text inside text/graphic clips Reading exposed text properties from MOGRTs Modifying exposed text properties in MOGRTs Reading and modifying other exposed MOGRT properties, such as: Color Number / Slider Checkbox Dropdown Other Essential Properties Ideally, these capabilities would work with both: MOGRTs created in Premiere Pro MOGRTs created in After Effects Why This Is ImportantPremiere Pro already has powerful transcription, text-based editing, graphics, MOGRT, and automation capabilities.However, without programmatic access to the actual text and exposed MOGRT properties, third-party developers cannot fully connect these systems.For example, with these APIs, developers could create tools that automatically:Transcribe → Generate text clips → Apply MOGRT designs → Replace text → Apply effectsThis could significantly reduce manual work for: YouTube editing Short-form video editing Interviews Podcasts Social media content Localization High-volume content production For editors who work with hundreds of text clips in a project, manually copying text into MOGRTs is extremely time-consuming.Suggested API DirectionIt would be very useful if UXP could provide a standardized way to access graphic and MOGRT properties, for example:getText()setText()getMOGRTProperties()getProperty()setProperty()or an equivalent API design that provides read/write access to exposed graphic properties.The exact API design is of course up to the Premiere Pro engineering team.The important requirement is that UXP extensions can reliably read and modify text and exposed properties of graphics and MOGRTs.Expected ImpactThis would enable a new category of Premiere Pro automation tools.Instead of automating only timeline operations, developers could build complete editing systems that connect transcription, graphics, templates, effects, and automated editing.As Premiere Pro continues moving extensibility toward UXP, I believe deeper access to text, graphics, and MOGRT properties would be extremely valuable for professional workflow automation.Thank you for considering this request.

emily_cecileKnown Participant

Please stop changing what's activated when you open a modal.Open for Voting

I am a Photoshop power user and have worked as a commercial retoucher for almost 15 years. With nearly every update, something seems to change in the click or tab order, and lately a couple of these changes have become particularly disruptive.Recently, I believe within the last two or three updates, the keyboard navigation for Hue/Saturation changed. I used to be able to hit cmd + u to make a quick adjustment, hit Tab twice to land on the Saturation field. Now I have to hit Tab seven times to get there.Similarly, when using Generative Fill, I used to be able to make a selection, click Generative Fill, and immediately start typing because the cursor was already active in the prompt field. Now I have to click into the prompt field before I can type.These sound like tiny changes, but when you work in Photoshop all day, every day, they aren't tiny. A huge amount of speed comes from muscle memory and deeply learned sequences of actions. Changing those sequences means retraining workflows that have been automatic for years.I appreciate continued development of Photoshop, but I wish more consideration were given to experienced daily users when changing established interaction patterns like keyboard focus, tab order, and default cursor placement.Thank you.P.S. If you're a Community Expert reading this, I'm specifically looking for a way to restore the previous behavior. If there isn't one, I don't need an explanation of why the new behavior is preferable or why I should adjust my workflow. Please leave this one for Adobe.