Bug 163293 - xfig text boxes for number entry fill up backwards
xfig text boxes for number entry fill up backwards
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xfig (Show other bugs)
4.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Stanislav Ochotnicky
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-14 17:01 EDT by Gordon Farquharson
Modified: 2010-06-07 09:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-07 09:13:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gordon Farquharson 2005-07-14 17:01:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
When entering numbers in an xfig text box (e.g. editing the depth in the edit panel), two single digital numbers (e.g. 4 followed by 5 for 45) will come out backwards. The this example 45 enetered comes out as 54.

Version-Release number of selected component (if applicable):
xfig-3.2.4-5

How reproducible:
Always

Steps to Reproduce:
1. Load xfig.
2. Draw a polyline.
3. Edit the properties of the line with by opening the edit panel.
4. Change the depth to 45 by deleting the current value and entering 4 followed by 5.
  

Actual Results:  54 appears.

Expected Results:  The result should have been 45 instead of 54.

Additional info:

Workaround (very annoying): enter 5 and then 4 for 45.
Comment 1 Stanislav Ochotnicky 2010-06-07 09:13:24 EDT
Closing this bug as won't fix. 

Reason:
This issue has been fixed in RHEL 5.x and RHEL 4.x is currently in "Production 2 Life Cycle Phase"[1], meaning that only bugs with priority HIGH and up are being fixed. I recommend upgrading to RHEL 5.x. You can contact your support representative if you have any questions.

[1] http://www.redhat.com/security/updates/errata/

Note You need to log in before you can comment on or make changes to this bug.