Bug 109267 - Ease of scripting of graphical interfaces
Summary: Ease of scripting of graphical interfaces
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: LO wishlist
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-18 18:24 UTC by Vladimir Dergachev
Modified: 2020-09-30 04:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Dergachev 2005-07-18 18:24:07 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    Compiled From Sources
OS:                Linux

I suggest the following bindings be implemented for all KDE/QT controls:

   * Control-Left click would copy a unique identifier of the control into the clipboard. This identifier would be usable with 
dcop, or some scripting tool, to edit or invoke the particular
control.

   * Control-Right click would popup a menu with several alternatives - unique identifier in the current desktop, unique
identifier relative to window, a command to open the window, whatever else people think handy.

In addition it would be handy to have a small graphical utility which would accept a paste action of the control identifier and be able to perform several actions with it, for example:

      * press control repeatedly, perhaps a predefined number of times, perhaps after fixed timestamps.

      * monitor control contents for change and make an alarm 
or execute other control when this happens.

      * allow construction of easy scripts.

                   thank you !

                       Vladimir Dergachev
Comment 1 Nate Graham 2020-09-30 04:20:45 UTC
>"...for all KDE/QT controls"
I'm afraid bug reports this broad generally aren't actionable. Screen readers generally allow you to do stuff like this though. You might try one and see if it meets your needs. If not, you can file specific bugs on what isn't working. We're always interested in improving the accessibility of our software.