New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HexDump Data Entry Not Functioning #103

Closed
GoogleCodeExporter opened this Issue Jul 2, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@GoogleCodeExporter

GoogleCodeExporter commented Jul 2, 2015

What steps will reproduce the problem?
1. Create new stream.
2. Edit new stream. Then at Protocol Selection Tab set Payload selection to Hex 
Dump.
3. Go to Protocol Data Tab and select HexDump section. Place curser in HexDump 
text/data area. Curser does not respond to keyed number entry. 
4. After many attempts data may be entered. No consistent way to make data 
entry work.

What is the expected output? What do you see instead? I expect to see the data 
I type show up in the HexDump definition area.


What version and revision of the product are you using (available in the
About dialog)? On what operating system? Version 0.5.1, Revision 74c9dcf830e3@. 
Windows XP and 2000.


Please provide any additional information below.


Original issue reported on code.google.com by lbmali...@gmail.com on 10 Apr 2013 at 9:06

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Jul 2, 2015

Experienced same problem on multiple machines with same verion.

Original comment by lbmali...@gmail.com on 10 Apr 2013 at 9:07

GoogleCodeExporter commented Jul 2, 2015

Experienced same problem on multiple machines with same verion.

Original comment by lbmali...@gmail.com on 10 Apr 2013 at 9:07

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Jul 2, 2015

I'm not able to replicate the issue. Note that only valid hexadecimal 
characters can be input i.e. 0-9 and A-F. And you can only input in the left 
hex pane, not the right ASCII pane which is view only.

Ostinato uses the qhexdump widget from http://code.google.com/p/qhexedit2/ - I 
looked at the issues fixed since the qhexdump release used by Ostinato and I 
don't see anything fixed (or open) similar to what you describe

Original comment by pstav...@gmail.com on 11 Apr 2013 at 12:13

  • Changed state: Reviewed

GoogleCodeExporter commented Jul 2, 2015

I'm not able to replicate the issue. Note that only valid hexadecimal 
characters can be input i.e. 0-9 and A-F. And you can only input in the left 
hex pane, not the right ASCII pane which is view only.

Ostinato uses the qhexdump widget from http://code.google.com/p/qhexedit2/ - I 
looked at the issues fixed since the qhexdump release used by Ostinato and I 
don't see anything fixed (or open) similar to what you describe

Original comment by pstav...@gmail.com on 11 Apr 2013 at 12:13

  • Changed state: Reviewed
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Jul 2, 2015

I appreciate you looking into this so quickly. I just spent some time
focused on this issue and found that although there is a blinking curser in
the test entry box, it does not mean it has been selected. You have to
right click once in the box before entering data. This appears to
consistently work.

Original comment by lbmali...@gmail.com on 11 Apr 2013 at 12:44

GoogleCodeExporter commented Jul 2, 2015

I appreciate you looking into this so quickly. I just spent some time
focused on this issue and found that although there is a blinking curser in
the test entry box, it does not mean it has been selected. You have to
right click once in the box before entering data. This appears to
consistently work.

Original comment by lbmali...@gmail.com on 11 Apr 2013 at 12:44

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Jul 2, 2015

Looks like http://code.google.com/p/qhexedit2/issues/detail?id=5&can=1

It's fixed in the latest qhexedit release which will get incorporated in the 
next Ostinato release.

Original comment by pstav...@gmail.com on 11 Apr 2013 at 12:58

  • Changed state: Accepted

GoogleCodeExporter commented Jul 2, 2015

Looks like http://code.google.com/p/qhexedit2/issues/detail?id=5&can=1

It's fixed in the latest qhexedit release which will get incorporated in the 
next Ostinato release.

Original comment by pstav...@gmail.com on 11 Apr 2013 at 12:58

  • Changed state: Accepted

@pstavirs pstavirs added bug and removed Type-Defect labels Jul 1, 2016

@pstavirs pstavirs closed this in 5c1aa6f Mar 13, 2017

cdm-work pushed a commit to cdm-work/ostinato that referenced this issue Dec 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment