Thread: FJV & FJW discussions

Yes, that is interesting. One more test, remove .fjv so now you're forced to use junction view provided by .fbl What do you see at that same junction?

Two more figures:

Spoiler: pics

The current route is the same as the previous one, but there is only one NNG junction (in data.zip = .fbl junction) -- only the second. In the previous case there are two junctions view.

[]'s

Thanks, that is quite interesting and odd. I never seen .fjv shown vector style junction. I wonder if NextGen show same vector style via .fjv? I need to revisit decoding .fjv but no time now.

Osiris4Isis,

see if this helps you better understand how Nextgen works with the FJV and FJW files:

Spoiler: pics

I'm sorry, I do not currently have an English language file. I will try to help with simple translations.

Translation:

Detalhes do conteúdo = Content Details
Visualização de junção = Junction View
Visualização de cruzamentos NG = Junction View NG


[]'s

If you ONLY use .fjv for NextGen, do you see vector style junction like Primo?

Osiris4Isis,

your question was very good. Answer: graphically speaking, visually, it stays the same way, unchanged.

Spoiler: pics

I believe the above figures answer what I said posts back: the two files, FJV and FJW, are equivalent, visually speaking.

[]'s


Edit: I note that in my first post (NextGen), the posted figures were based only on the FJW file. Identical to these figures above.

PS: Osiris4Isis = Hadit & Nuit?

So there is no way to get .fjv (raster junction) to work under NextGen? That is VERY odd, make sure NextGen only see .fjv by checking About->Content->Junction View

The version of NextGen I am using reads both .fjw and Fjv files. The first image below is with ONLY fjv file in the map folder, and the second is with ONLY fjw in the folder. There is almost no difference

Spoiler: pics

[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]

What is map and proggy version?