Continuous as default in Windows, fixed for 2026?

[alexperez]

Note to moderators: I originally posted this in the General thread by mistake, but I realized it belongs here under the specific TextMaker section where the developers can see it. Please feel free to delete my copy in the General section.

Subject: Why does TextMaker break its own value proposition when opening foreign .docx files?
Dear SoftMaker Team,
I recently migrated to SoftMaker Office because your core marketing promise is clear: you offer a professional, high-fidelity alternative to Microsoft Word that respects user focus and workflow continuity.
However, I have run into a fascinating design logic flaw in the latest version of TextMaker that completely undercuts this promise.
When a user opens a third-party .docx file (from a download, cloud drive, or external script), TextMaker completely ignores the user’s global default template environment (Normal.tmvx) and defaults to forcing a Continuous view layout.
Let's look at this through a simple Socratic lens:
1. What is the primary target audience of an alternative office suite? Users who want a reliable, focused, and seamless document editing experience mimicking professional paper standards (Standard View).
2. What percentage of professional writers, lawyers, or corporate operators choose to edit their daily business files in "Continuous stream text" view? Effectively zero.
3. If the software encounters a document missing explicit Microsoft view metadata, why does the engine fallback to an absolute edge-case layout (Continuous view) rather than respecting the global default view (Standard View) chosen by the user in their active template?
By forcing the engine to assume the user wants Continuous view on every single unknown document, you are introducing a repetitive micro-frustration. The user has to manually toggle the View menu back to Standard style for every file in their folder structure, completely breaking workflow efficiency.
The Simple Fix:
In your codebase's file import module, look at your fallback handler for files lacking explicit view metadata tags. Simply change the default fallback hook variable from VIEW_CONTINUOUS to look at the active template configuration path (VIEW_STANDARD / Normal.tmvx).
Alternatively, please restore the "Default view mode for opening files" option within the Options menu configuration so the user has the autonomy to declare their preference globally.
I would love to understand the engineering logic behind keeping Continuous view as a hardcoded fallback, and if your team can push this incredibly simple change into an upcoming Service Pack update to fix this major usability hurdle.
Best regards,
Alex