General ⇒ Make Yap default DVI Viewer in TXC2b1

[mdrapk]

Hi all, I hope this is the right forum for my question and I also hope I'm submitting this correctly.

I installed TeXnicCenter 2 beta 1 alongside ProTeXt (MiKTeX). When I run build & view, TXC2b1 tells me that Yap is not the default viewer and asks if I would like to make it so. I click yes and everything works fine. But I always get that message. Not the end of the world if I can't fix it but it would be nice not to have to click yes every time.

[mdrapk]

Hi all,
My question has been up for several days now and received 20+ looks, but no one has responded. That leads me to wonder if it is unclear or if I've posted it in the wrong place.

[MartinC]

Could you show us more details? What are your build profile settings?

[mdrapk]

Hi, thanks for the interest.
The 'viewer' tab in the build profile reads:

C:\Program Files\MiKTeX 2.9\miktex\bin\x64\yap.exe

Then ...

View Project
Cmd line args:

-1 "%bm.dvi"

Then ...

Forward Search
Cmd line args
-1 -s %l"%Wc" "%bm.dvi"

While I grasp the basic concept of passing arguments to called programs, these particular calls do not mean anything to me. I assumed that since TXC was able to find yap and ask me (repeatedly) if I wanted to make the default that it wasn't a 'path' issue, but something else. But then, what do I know!

Thanks for any help. I was wrong in my first post about it not being the end of the world - it is becoming truly annoying to have to respond Yes every time I build & view. And since I'm just learning LaTeX, I'm doing it a lot. I hope that as I become more comfortable with the markup language I will need the reassurance of 'views' less often. But right now it's kinda critical.

[MartinC]

I found this where someone had a problem similar to yours:

http://comments.gmane.org/gmane.editors.winedt/6180

The problem is on the Yap side, not TxC. In his case, he had an old Miktex 2.8 installation that caused the problem.

[mdrapk]

Thanks for the interest and I followed the link. I never installed MikTeX before the 2.9 version, so that can't be the problem. I took a look at the registry - it was mentioned in the thread - for all the good it did me since I'm not sure what I'm looking for. Nothing jumped out at me. It seems odd that if there is only one (and never was any other) version of yap except the 2.9, AND TxC finds it and uses it, that it does not accept it as the default. That seems a TxC issue, no?

But then, I am working in a Windows environment - all things are possible. Don't give up on me yet.
Tony

[MartinC]

I think you should ask for this on the Miktex forum.

[mdrapk]

Perhaps you're right, but as the blurb below hints at, I may be in the wrong universe entirely. Nevertheless, thanks MartinC for hanging in there with me. It's lonely in the land of failure.

For anyone following this thread, the problem lies (I believe) with Windows, not with either application. Just for grins and giggles I located a .dvi file and when I double clicked on it, Windows launched yap but then noted that it was not the default viewer. Deja Vu all over again. The message I'd been seeing was not a TxC message but a Win7 override. With that knowledge I went through the Win7 process to establish default apps for file types, but to no avail. Win7 reported yap as the "default" viewer in the dialogue box, but I still received the message upon running TxC. I then downloaded a third party utility from CNET (cbsidim-tri_11...) to see if I could force Windows into seeing yap as the viewer. No dice. BTW, the app tries to add a few features to your system so beware.

Anyway, to add insult to injury (self inflicted) I used the app to clear the file association in the hopes of starting again. Then everything got crazy and I now do not have viewer capability at all.

So much for going digital with my lectures. Between the time I've spent trying to learn TeX and the grief of trying to make a native Unix structure work under Windows I could have built Noah's Ark. Still, my compliments to TeX as a construct (thank you DEK) and the TxC folks for creating a fine development environment.

Now, if there's a Windows techie out there watching this thread, please jump in. I gather from my searches that Win Vista & 7 had file association issues that have not been addressed, so please, help your users. You could be anonymous, we wouldn't mind.

[mdrapk]

I solved my problem but at this point I'm not exactly sure which of the many things I did solved it. And since I got the sense from the relative lack of interest that this was not a general problem, I will not bother folks with the details. However, if anyone else runs into this they can re-open the thread and I will be happy to tell them what I did, off line if need be.
Thanks all for the help and interest.

[MartinC]

Why don't you tell us? It could be useful for other users.