Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
gmsh
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Romin Tomasetti
gmsh
Commits
ee96c69e
Commit
ee96c69e
authored
7 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
fix doc
parent
23ebcf67
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
demos/api/t1.cpp
+8
-8
8 additions, 8 deletions
demos/api/t1.cpp
with
8 additions
and
8 deletions
demos/api/t1.cpp
+
8
−
8
View file @
ee96c69e
...
...
@@ -15,7 +15,7 @@ int main(int argc, char **argv)
// By default Gmsh will not print out any messages: in order to output
// messages on the terminal, just set the standard Gmsh option
// "General.Terminal" (same format and meaning as in .geo files) using
// gmsh
O
ption
S
etNumber():
// gmsh
::o
ption
::s
etNumber():
gmsh
::
option
::
setNumber
(
"General.Terminal"
,
1
);
// This adds a new model, named "t1". If gmsh::model::add() is not called, a
...
...
@@ -24,8 +24,8 @@ int main(int argc, char **argv)
// The C++ API provides direct access to the internal CAD kernels. The
// built-in CAD kernel was used in t1.geo: the corresponding API functions
//
have
the "gmsh
ModeGeo" prefix
. To create geometrical points with
the
// built-in CAD kernel, one thus uses gmsh
M
odel
GeoA
ddPoint():
//
live in
the "gmsh
::model::geo" namespace
. To create geometrical points with
//
the
built-in CAD kernel, one thus uses gmsh
::m
odel
::geo::a
ddPoint():
//
// - the first 3 arguments are the point coordinates (x, y, z)
//
...
...
@@ -65,11 +65,11 @@ int main(int argc, char **argv)
// Before it can be meshed, the internal CAD representation must be
// synchronized with the Gmsh model, which will create the relevant Gmsh data
// structures. This is achieved by the gmsh
M
odel
GeoS
ynchronize() API
call for
// the built-in CAD kernel. Synchronizations can be called at any
time, but
// they involve a non trivial amount of processing; so while you
could
// synchronize the internal CAD data after every CAD command, it is
usually
// better to minimize the number of synchronization points.
// structures. This is achieved by the gmsh
::m
odel
::geo::s
ynchronize() API
//
call for
the built-in CAD kernel. Synchronizations can be called at any
//
time, but
they involve a non trivial amount of processing; so while you
//
could
synchronize the internal CAD data after every CAD command, it is
//
usually
better to minimize the number of synchronization points.
gmsh
::
model
::
geo
::
synchronize
();
// We can then generate a 2D mesh...
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment