This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Installer UI not taking keyboard input.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 22, 2013
06:05 AM
Installer UI not taking keyboard input.
Recently we upgraded installer from 2009 to 2012.
We are seeing a weird behavior in "some" unix machine(using X window).
While installing the product created by using InstallAnywhere2012, it does NOT take keyboard input.
This happens only in some machine.
I could see the release notes of 2012 SP1:
IOA-000066700 When end users navigate between panels, the cursor is no longer positioned in
read-only locations on the Choose Install Directory panel or the Get User Input -
Advanced panel. Previously in some scenarios, the cursor was positioned next
to read-only text.
I thought may be it is similar issue, and tried upgrading to InstallAnywhere2012SP1.
But that did not solve the purpose.
Is it an issue in installer side? if not where should we look into for fixing it?
We are seeing a weird behavior in "some" unix machine(using X window).
While installing the product created by using InstallAnywhere2012, it does NOT take keyboard input.
This happens only in some machine.
I could see the release notes of 2012 SP1:
IOA-000066700 When end users navigate between panels, the cursor is no longer positioned in
read-only locations on the Choose Install Directory panel or the Get User Input -
Advanced panel. Previously in some scenarios, the cursor was positioned next
to read-only text.
I thought may be it is similar issue, and tried upgrading to InstallAnywhere2012SP1.
But that did not solve the purpose.
Is it an issue in installer side? if not where should we look into for fixing it?
(10) Replies