Measurement codes(male)

Newbies
1

Hi

im pete , and i was just wondering if new measurement area codes can be added for the male for

many thanks

3 curtidas
2

Welcome @peterd

Male codes for what measuremets?

2 curtidas
3

hi

leg opening for brief boxer brief and trunk,

inseams for the above , pouch depth and and drop

3 curtidas
4

Hi @peterd

The inseam on boxers is a pattern measurment not a body measurement, and generally can be anywhere from 3-7". Any measurement that is not a body measutment should be a Custom Variable. That said I would think the leg opening would be the thigh measurement, and the pouch and drop can probably be (or calculated from) the crotch and rise lengths. The pouch is more a question of volume where it is more analogous to a cup size in a bra… something you normally don’t directly measure.

Not sure I see any need to add any new “Known” measurements here to ME, but I’m certainly open to other opinions or being convined otherwise. :slightly_smiling_face:

2 curtidas
5

Hey @Douglas - Tagging onto this thread with a question. I’ve just started playing around with the app and I can’t seem to find a men’s chest circ measurement. I only see “bust” circ (though there are other “chest” measurements listed). Should I just use “bust circ” or am I missing something? Thanks!

2 curtidas
6

I’ve always just used bust_circ. If you choose you can create a custom measurement named “chest” and just use bust_circ as the formula. Also since most mens pattern systems use “chest scale” or 1/2 the chest measurement… I create a custom measurement “chestScale” with bust_circ / 2 as the formula.

2 curtidas
7

Ah! Good tips, thank you!

2 curtidas
8

If we’re to make recommendations on how to create garments, I’d like to know how to calculate these derived measurements.

The bra cup size is calculated as ratio between highbust and bust, or it can be calculated as a ratio between bust and lowbust. Typically the ratio between highbust and bust is more accurate.

Pouch is probably a similar ratio, but I don’t know which measurements are involved. @peterd, or anyone out there, can you provide the measurements used to derive the pouch measurement?

@SeanMP - It may be that we add chest measurements, such as chest_circ, chest_arc_f, chest_arc_b, as this is important for men to be confident that they’re using a measurement that applies to them. We would enforce that chest measurements and bust measurements are the same. I’m working on a plan. An evil master plan that uses measurement number as the key, which would allow multiple measurement names to refer to the same number. This might require a huge rewrite, though, so it may never happen.

2 curtidas
9

If you go by number how are you supposed to know if it refers to bust_circ or chest_circ? A key has to be unique… so you can’t have the same key (number) point to different values (names). However you can can have 2 different keys point to the same value.

Which is why we retreieve a measurement by name… then get it’s number, full name. formula, and description by name. For ex:

AddCell(getMeasurementNumber(meash->GetName()), currentRow, ColumnNumber, Qt::AlignVCenter);
AddCell(qApp->translateVariables()->guiText(meash->GetName()), currentRow, ColumnFullName, Qt::AlignVCenter);

And yes.. it would take a completely useless rewrite.

That being said… adding chest_circ, chest_arc_f, chest_arc_b would be a simple task to do.

2 curtidas
10

I’m an SQL database person, so I’m used to having many-to-one relationships where several items map to a unique key field.

The unique key field is in the master database, which has formula field (which can be blank) and a blob or image field for the measurement image – the master database is language independent.

Each language database is keyed to the master database, and holds the language’s measurement name and description field – the measurement names can contain bust_circ and chest_circ that point to the same key id in the master database.

The measurement file contains numbers and values. This is all pulled together in the SeamlyMe application.

The formula parser can be rewritten to !enable dropdowns! to select the measurement name in the selected language, just like modern coding IDEs.

This makes it easier to add new measurements, to mark in the master database which patternmaking system a measurement uses.

There are other ways to implement this relational strategy other than straight-up SQL relational databases. This would be fast and spiffy, enabling easier formula creation.

2 curtidas
11

Right… that makes sense if for ex: you have multiple invoices for a single buyer. You won’t have mutltiple buyers on a single invoice. In our case the measurement is unique, not the diagram number.

We’re storing measurements in a Qt QMap container that consists of a unique QString (name) as the key and a pointer to the variable data struct as the value. It could be the same many-to-one… many names to one diagram number (inside the variable struct) .

QMap<QString, QSharedPointer<MeasurementVariable>

Again… if we could (which we can’t) - and you search by number and return 2 different names… how would you know what name to use?

A QMap like this…

QMap<int, QSharedPointer<MeasurementVariable>

can not store 2 different measurement structs with the same key number. QMap’s by nature are sorted by key, and if you insert a new pair and the key already exists, it will overwrite the old pair.

QMap<Key, T>::iterator QMap::insert(const Key &key, const T &value)

Inserts a new item with the key key and a value of value.

If there is already an item with the key key, that item’s value is replaced with value.

Returns an iterator pointing to the new/updated element.

2 curtidas