Bug #22948 No reaction to double click, and no context menue on selected 'View'
Submitted: 3 Oct 2006 16:42 Modified: 4 Oct 2006 9:14
Reporter: Heinz Schweitzer (Gold Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.4 RC OS:Windows (XP)
Assigned to: CPU Architecture:Any

[3 Oct 2006 16:42] Heinz Schweitzer
Description:
No reaction to double click, and no context menue on selected 'View'
Similar to Bug #22734

**********************************************
systeminformation
**********************************************
MySQL Administrator 1.2.4 RC (German)
MySQL-Server-Information
--------------------------------------------------------------------------------
Mit MySQL-Serverinstanz verbunden
  Benutzername:            root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Serverinformation
  MySQL-Version:           MySQL 5.0.18-nt via TCP/IP
  Netzwerkname:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Clientinformation
  Version:                 MySQL Client Version 5.0.11
  Netzwerkname:            hgs
  IP:                      192.168.2.5
  Betriebssystem:          Windows XP
  Hardware:                Intel(R) Pentium(R) 4 CPU 2.00GHz, 504 MB RAM

How to repeat:

Open the Mysql Administrator (German localized)
select Kataloge-->mysql
In the right pane activate the 'View' tab

In there just create a simple view if there is none (like
CREATE OR REPLACE VIEW `mysql`.`aaa` AS SELECT * from db.
Save the view)

Try to open the view with 'double click'
---> nothing happens. 
I expected to open the view in an editor.

Select the view and press the right mouse button.
---> No context menue. 
I expected a context menu to pop up to offer the same functionality
as the buttons at the bottom.
[4 Oct 2006 9:14] Sveta Smirnova
Thank you for the report.

I mark it as duplicate of the Bug #22734, because problem is same.