Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)

Method note for “Crystal reflections: why a dark patch is not a coating test”: use “Compare multiple controlled angles and describe the visible observation without asserting…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Reader check for “Comparing dial colour under different lighting”: distinguish the discussion point “Compare controlled images where available and avoid calling a…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.

Case 54 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained · source wording exercise

Method note for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: use “Measure with a ruler marked in millimetres, ideally…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Retain the source wording beside any paraphrase.

Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.

Case 20 — What a water-resistance claim does and does not establish

Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “List confirmed differences separately from seller descriptions and date the comparison…”; the related point is “Match reference, dimensions and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.

Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.

Case 2 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

Case 35 — Bracelet fit: measuring the usable clasp adjustment

Summary draft for “Bracelet fit: measuring the usable clasp adjustment”: the answer addresses “Record wrist circumference, removable links and the clasp…”; the related point is “Request the closed bracelet circumference rather than inferring…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.

Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

Case 16 — Forum comparison archive: link the evidence and the correction

Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

Case 1 — Lume questions: why does my lume fade so quickly, and how should I compare it?

A practical test without a camera: charge both watches the same way, sit in a dark room, and check readability at 5 minutes, 30 minutes and 2 hours. Write down which you can still read the time on. It's subjective but repeatable, and more useful than a single photo.

Case 25 — Maintenance question: how do I tell if an automatic actually needs service?

The calendar interval is a conservative default, not a rule. Useful signs, in rough order of seriousness: power reserve noticeably shorter than spec from full wind, rate drifting outside its usual range, the watch stopping on the wrist, gritty or rough winding, and the date changing slowly or late.

Method note for “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: use “First, a clarifying question: how many links are on each…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Viewing 15 posts - 1 through 15 (of 24 total)