Modify

Opened 11 years ago

Closed 10 years ago

#140 closed Feature Request (Completed)

Add ToolbarWindow32 information on buttons

Reported by: junkew@… Owned by: Jpm
Milestone: 3.3.1.0 Component: Au3Info
Version: Severity:
Keywords: Cc:

Description

Would be nice if buttons on toolbar windows are recognized or at least some initial information can be spyed on.

Some (partial) code like below retrieves some usefull information
Code acts now on wordphrase like Toolbar but can imagine trigger should be something less classname dependent. (Class tested on = ToolbarWindow32)

if stringinstr($sClassname,"Toolbar") > 0 Then
	$tbCount = _GUICtrlToolbar_ButtonCount($hWnd)
	for $i=0 to $tbcount -1
		;Determine rectangle and check matching area
		$aRect = _GUICtrlToolbar_GetButtonRect ($hWnd, _GUICtrlToolbar_IndexToCommand($hWnd, $i))
		$mPos=mousegetpos()
		$wPos=wingetpos($hWnd)
		if (($mPos[0] - $wPos[0]) > $arect[0] ) and (($mPos[0] - $wPos[0]) < $arect[2] ) _
		And (($mPos[1] - $wPos[1]) > $arect[1] ) and (($mPos[1] - $wPos[1]) < $arect[3] ) Then
			$tbText = "[Index: "     & $i & _ 
			          " CommandID: " & _GUICtrlToolbar_IndexToCommand($hWnd, $i) & _
					  " text: "      & _GUICtrlToolbar_GetButtonText($hWnd, $i) & " ]"
		endif	
	next
endIf

Wishes
"Must"

  • Show initially information on index, commandid, text, tooltip and area of the button where mouse is hovering over

"Should"

  • Highlight/rubberband the button hovering over

Attachments (0)

Change History (9)

comment:1 Changed 11 years ago by TicketCleanup

  • Version 3.2.10.0 deleted

Automatic ticket cleanup.

comment:2 Changed 11 years ago by TicketCleanup

  • Milestone Future Release deleted

Automatic ticket cleanup.

comment:3 follow-up: Changed 11 years ago by Gary

  • Resolution set to Rejected
  • Status changed from new to closed

Write a wrapper function of what you want.

I believe also much of what you are wanting can be done thru WM_NOTIFY.

comment:4 in reply to: ↑ 3 Changed 11 years ago by junkew@…

  • Resolution Rejected deleted
  • Status changed from closed to reopened

Replying to Gary:

Write a wrapper function of what you want.

I believe also much of what you are wanting can be done thru WM_NOTIFY.

Are we talking about the same here. I am talking about the AU3INFO.EXE window spying tool. I understand I can write functions to analyze an hwnd ToolbarWindow32 deeper but that means run a function before analysis can be done. I feel that the AutoIt Window Info tool is build for that purpose and now its only showing the main window information of a toolbar but not the actual buttons that are on the toolbar.

I am not talking about activating/clicking the buttons thru code but having the AU3INFO.EXE tool immediately showing me the commandid's tooltips etc. of the buttons on the toolbar so I can easily find out what code I have to write to use it actually.

comment:5 follow-up: Changed 11 years ago by Gary

Well considering you never once mentioned au3info in the original post, all anyone could do was assume.

comment:6 in reply to: ↑ 5 Changed 11 years ago by Valik

Replying to Gary:

Well considering you never once mentioned au3info in the original post, all anyone could do was assume.

Actually, he did set the component to Au3Info. Still, though, I don't disagree. It should have been mentioned in the post.

comment:7 Changed 11 years ago by junkew@…

Sorry for not mentioning it in the description itself but I thought as it was in the component selected it was clear.

What I currently experience with AutoIT is that I can do a lot with coding but have to write scripts to find out more details on for example toolbars and the ID's of the actual buttons I want to click before I actually can write my actual script.

For ease of use it would be handy if that information is immediately shown by AU3Info. I don't care if its the code I supplied or otherwise implemented but the more AU3Info immediately shows the more time it will save me in coding.

comment:8 Changed 11 years ago by Zedna

It sounds like VERY usefull idea.
I vote for this feature too.

comment:9 Changed 10 years ago by Jpm

  • Milestone set to 3.3.1.0
  • Owner set to Jpm
  • Resolution set to Completed
  • Status changed from reopened to closed

Added in version: 3.3.1.0

Guidelines for posting comments:

  • You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
  • In-depth discussions should take place on the forum.

For more information see the full version of the ticket guidelines here.

Add Comment

Modify Ticket

Action
as closed The owner will remain Jpm.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.