Ticket #314 (new behaviour)

Opened 15 months ago

Last modified 2 months ago

PaddingField use only 0 as a padding

Reported by: getxsick Owned by: getxsick
Priority: low Milestone: UMPA 0.4.0 - autogeneration+IPv6
Component: UMPA Version: current svn
Keywords: Cc:

Description

It's OK for common issues but it deny to idea of UMPA where you can edit any bit you want.

Propably we should allow to use any padding value and "somehow" convert it for padding bits.

Attachments

Change History

Changed 15 months ago by getxsick

  • priority changed from medium to low

anyway, and read again my own code and what realized is: value for PaddingField? is being used to set length of bits manually instead of generate necessary length.

so, if we wanna add possibility to change padding digit we should change a way to set length of bits.

personally, i'm not sure if it's worth. more important is to set length than what will padd it. but maybe i'm wrong. any suggestions by others?

Changed 2 months ago by kosma

  • milestone set to UMPA 0.4.0 - autogeneration+IPv6

Add/Change #314 (PaddingField use only 0 as a padding)

Author



Action
as new
 
Note: See TracTickets for help on using tickets.