-
Notifications
You must be signed in to change notification settings - Fork 35
Batch entry dimensions adjustment #468
Comments
Which window types also support batch entry? I want to test other cases. The problem is, if we want to do it without adding new widget type i have to make some dirty hack, and it may cause issues in future/other window types. |
atm the only windows with batch entries are sales/purchase order, customer/vendor empties. So basically only Windows. does this answers your question? |
Yes thank you. Im gonna deliver some achievements soon. |
@metas-lc agree. the reason for making the field bigger is mostly to have more space for the product name. @damianprzygodzki can u please take care? |
Im not sure that changing design here will be good for consistency. I was thinking about solution here, to move packing (or other additional fields) to the left. Do we want to change it in every place for lookup? |
So you want more space for long product name OR packaging name closer to product name. You cannot have both because it excludes each other. :) |
@damianprzygodzki @cadavre |
moving it to current milestone |
As a default behaviour: Optional: |
Shouldn't we close it? Nothing to fix here and possible discussion should be moved to lookup revamp issue #600 |
i think we shall implement on of cadavre's suggestions. I just need to get to it. |
Still it is a case of new version of lookup, possible duplicate. |
Ok, then i am closing it and the work shall be done on #600. |
Type of issue
Feature request
Current behavior
The fields for Combined Product +Packing and Quantity have the same width. Often the Product name, with important information is cut off from Packing material.
Expected behavior
We need more space for the combined Product Field especially more for the product (a) itself. The Packing element (b) can be reduced in width. Same the quantity field (c).
Please also add a small separator are between the elements.
Steps to reproduce
Open any window w/ batch entry possibility, for example, window/143/
The text was updated successfully, but these errors were encountered: