Does anyone know what is causing this?
freeglut (x): Unable to create direct context rendering for window 'Mesh'
This may hurt performance.
<< close all views to continue >>
D Closed view "Mesh", window #1
X Error of failed request: GLXBadContextTag
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 51
Current serial number in output stream: 51
The code is as follows:
// Display the mesh.
// (100, 0) is the upper left corner position, 600 x 500 is the window
size
MeshView mview("Hello world!", 100, 0, 600, 500);
mview.show(&mesh);
// Wait for the view to be closed.
View::wait();
I do get an image on display but shortly after closing the window the
job crashes.
Thanks,
--
Valmor
--
You received this message because you are subscribed to the Google Groups "hermes2d" group.
To post to this group, send email to herm...@googlegroups.com.
To unsubscribe from this group, send email to hermes2d+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hermes2d?hl=en.
Pavel,
I created a fork from your hermes2d repo, cloned, made changes,
committed, and pushed to my repo
-> git push g...@github.com:val-github/hermes2d.git change
Does github send you an e-mail or notice that changes were made?
Thanks,
--
Valmor
No, but you can send a so called "pull request" on github (just click
on that button, you should see it) and then Pavel will get an email.
Ondrej
A related question. If I do a
git pull git://github.com/val-github/hermes2d.git change
on my repo forked from Pavel's, does this mean that I get all the mods
pushed into Pavel's change branch? Or do I have to pull from his repo on
my local branch and do a push on my github repo?
Still reading about github and git remote...
Thanks,
--
Valmor
Yes.
> my local branch and do a push on my github repo?
github is an unrelated thing --- you can push in there if you want,
then it will also appear online at your github, but you don't have to.
Ondrej
What is confusing me is that when I look at the commit history on my repo
http://github.com/val-github/hermes2d/commits/change
and compare to Pavel's
http://github.com/solin/hermes2d/commits/change
I don't see the changes in Pavel's reflected on mine. Therefore for my
github repo to have the latest changes, I need to pull from Pavel's into
my local copy and push into my github repo. Is this correct? Or is there
a way to update my github repo (meaning get the new mods from Pavel's)
through the github website?
Thanks,
--
Valmor
-------------------------------------------------
This application uses Hermes2D
Hermes2D is a C++ library for rapid
development of adaptive FEM and hp-FEM solvers
developed by the hp-FEM group at UNR
and distributed under the GPL license.
For more details visit http://hpfem.org/.
-------------------------------------------------
I Length of bdry 1 = 2
I Length of bdry 2 = 2
I Length of bdry 3 = 2
I Length of bdry 4 = 2
I Computed perimeter = 8
I Exact perimeter = 8
<< close all views to continue >>
D Closed view "Mesh", window #1
Success!
Yes.
Or is there
> a way to update my github repo (meaning get the new mods from Pavel's)
> through the github website?
>
> Thanks,
>
> --
> Valmor
>
There is also a way to do it through the website. But I suggest you do
it from the command line.
Ondrej
Pavel
When possible please try the other CASE in main.cpp. You will need to change
const Cases CASE = SQUARE; // pick the case from the enum above
I wonder whether my version of freeglut is problematic. I am using
freeglut-2.4.0; just guessing from the context rendering error message.
Thanks,
--
Valmor
I should have read this
http://help.github.com/forking/
before creating my github repo. I think I got it now.
Thanks,
--
Valmor
Great, this takes some time.
Pavel
Exactly.
Ondrej
I see it in your commit history:
Merge remote branch 'valmor/change' into valmor
I also updated the upstream repo of my fork
Merge remote branch 'upstream/change' into change
I have added some comments to the domain-perimeter/main.cpp file to test
how this fork push/pull stuff works and you should have received a message.
--
Valmor
Yes. I noticed that you guys typically create a github repo and push a
local clone into it. Then others can merge into their own repo.
I think I understand the difference.
Forking makes things a little more specific. When I forked from Pavel's
change branch and cloned a local repo, I did not have to checkout the
branch. I guess cloning a specific branch would have the same effect
(?). I don't know whether forking facilitates things but my push command
into the fork is simply
git push origin change
and the pull
git pull upstream change
Still trying out these things on a working basis...
Thanks for the feedback.
--
Valmor
[snip]
>
> Erick
>
[snip]
Thanks!
Pavel
Will do it. A pull request from my fork of your change branch will be
sent to you. Yes I have been wondering about the logic of tests and
examples. There is a test/, test/example, test/tutorial.
--
Valmor
Yes, and also tests/benchmarks/. These tests are in groups corresponding to
the directories tutorial, benchmarks/, and examples/. Plus there are
additional tests for the mesh, projections, shape functions, etc.
Pavel
>
> --
> Valmor