• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

Text Input Tool not working reliably in 24.2.0 BETA (Build 68)

Community Beginner ,
Jan 11, 2024 Jan 11, 2024

Copy link to clipboard

Copied

Ever since upgrading to this Beta version of the program, I am having semi-frequent issues with inputting text in my timeline.  When I attempt to edit the text of an existing Text item, I will sometimes need to select the Type Tool multiple times over, otherwise it will interpret my inputs as keyboard shortcuts instead.  On occasion, even selecting Type Tool over and over will not allow me to appropriately edit/input text.  I try to click on a part of the textbox with the Type Tool selected but it will not actually place the typing cursor into the box and I am unable to make any changes to it.  Trying to highlight a swath of text in the box nets the same result, it is immediately deselected.  I have not been able to trace a common factor that triggers this.  Restarting the program seems to fix it, but I never had this issue in previous versions.

 

App version: 24.2.0 BETA (Build 68)

Platform & OS Version:  Windows 11, Version 22H2 (OS Build 22621.2861)

Bug Unresolved

Views

508

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jan 12, 2024 Jan 12, 2024

Thank you for reporting this problem to us. This sounds the same as a bug we recently fixed. If possible, could you try it again from scratch using Pr24.2xBeta073 or higher on that same Windows system? Thanks in advance.

Votes

Translate

Translate
4 Comments
Adobe Employee ,
Jan 12, 2024 Jan 12, 2024

Copy link to clipboard

Copied

Thank you for reporting this problem to us. This sounds the same as a bug we recently fixed. If possible, could you try it again from scratch using Pr24.2xBeta073 or higher on that same Windows system? Thanks in advance.

Votes

Translate

Translate

Report

Report
Community Expert ,
Jan 12, 2024 Jan 12, 2024

Copy link to clipboard

Copied

Moved to beta forum.

provide feedback.png

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 16, 2024 Jan 16, 2024

Copy link to clipboard

Copied

Thanks @jstrawn!!  After running the latest update yesterday (Pr24.2xBeta78 at the time), this issue seems to be dealt with!

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 16, 2024 Jan 16, 2024

Copy link to clipboard

Copied

LATEST

Thanks Ann!  Apologies for the initial miscategorization!

Votes

Translate

Translate

Report

Report
Resources