NI Discussion Forum Upgrade - August 13, 2008

[smercurio_fc]

More bizarre behavior with the new editor. At least I think it's the editor.

I copied a paragraph from the LabVIEW Help. This was the 5th paragraph in the "Using Project Libraries" topic. In the editor the text appeared just fine. When I submitted the reply the text that appeared looked like this:

Using Project Libraries var L_helpType = "STD_ENG"; Dim hasPlayer, playerversion hasPlayer = false playerversion = 10 Do While playerversion > 0 On Error Resume Next hasPlayer = (IsObject(CreateObject("ShockwaveFlash.ShockwaveFlash." & playerversion))) If hasPlayer = true Then Exit Do playerversion = playerversion - 1 Loop is_FlashVersion = playerversion is_Flash = hasPlayer
Use project libraries to qualify the names of VIs and other LabVIEW files. LabVIEW identifies VIs by filename, so LabVIEW unintentionally might load and reference a VI because the VI has the same filename as another VI, a problem known as cross-linking. When a VI is part of a project library, LabVIEW qualifies the VI name with the project library name to avoid cross-linking. A qualified filename includes the filename and the owning project library filename.

 When I went to try to edit the message to fix it, for a brief moment I saw VB-like code with "Dim" statements. I changed to HTML mode and saw this:

Dim hasPlayer, playerversion
hasPlayer = false
playerversion = 10
Do While playerversion > 0
On Error Resume Next
hasPlayer = (IsObject(CreateObject("ShockwaveFlash.ShockwaveFlash." & playerversion)))
If hasPlayer = true Then Exit Do
playerversion = playerversion - 1
Loop
is_FlashVersion = playerversion
is_Flash = hasPlayer

Use project libraries to qualify the names of VIs and other
LabVIEW files. LabVIEW identifies VIs by filename, so LabVIEW unintentionally
might load and reference a VI because the VI has the same filename as another
VI, a problem known as cross-linking. When a VI is part of a project library,
LabVIEW qualifies the VI name with the project library name to avoid
cross-linking. A qualified filename includes the filename and the owning project
library filename.

[smercurio_fc]

---

smercurio_fc wrote:
Another oddity encountered with the new edit message area. If you go back to try to edit your message, and say your message contained blank lines, if you click on one of those blank lines, it seems that there's a space that gets added at the beginning of the line. I'm almost positive this wasn't there before. Seen on Firefox 3.

---

I think I may have found out what's causing this. Apparently the new editor is replacing the space at the end of line with &nbsp; and then a space and then a </p>. At least that's what I see when I switch to HTML mode. When you press the backspace key it seems to erase too much. This seems to happen only under Firefox. 

I also noticed that the editor places spaces on new lines for no apparent reason. Again, it's because it's adding the &nbsp; before the </p>. It makes no sense why it does this. This happens on either Firefox or IE.

[Laura F.]

I can reproduce the editor window moving in IE7, but not Firefox 2.  Ben & altenbach - can you confirm you are using IE?

For me, the window moves as I start to move my mouse back towards the scroll bar after typing a few lines.

I am reporting the issue now. 

Thanks,

Laura 

Edit:  after playing around with this longer, the window moves at other times as well and I can see this is VERY frustrating. 

Message Edited by Laura F. on 09-02-2008 11:37 AM

[Laura F.]

Hi CC,

I was not aware of any maintenance that happened this weekend.  Do you know about how long that Forums Closed message lasted for you?  Or is it still happening?  

Thanks,

Laura 

Message Edited by Laura F. on 09-02-2008 11:36 AM

[altenbach]

---

Laura F. wrote:

Ben & altenbach - can you confirm you are using IE?

---

Yes, I am using IE.

[Ben]

IE6 at work and IE7 at home.

Ben

[Laura F.]

---

smercurio_fc wrote:

---

smercurio_fc wrote:
Another oddity encountered with the new edit message area. If you go back to try to edit your message, and say your message contained blank lines, if you click on one of those blank lines, it seems that there's a space that gets added at the beginning of the line. I'm almost positive this wasn't there before. Seen on Firefox 3.

---

I think I may have found out what's causing this. Apparently the new editor is replacing the space at the end of line with &nbsp; and then a space and then a </p>. At least that's what I see when I switch to HTML mode. When you press the backspace key it seems to erase too much. This seems to happen only under Firefox. 

I also noticed that the editor places spaces on new lines for no apparent reason. Again, it's because it's adding the &nbsp; before the </p>. It makes no sense why it does this. This happens on either Firefox or IE.

---

OK - I've reproduced this as well.

Thanks!

Laura 

[chilly_charly]

---

Laura F. a écrit:  [...] I was not aware of any maintenance that happened this weekend.  Do you know about how long that Forums Closed message lasted for you?  Or is it still happening?  [...]

---

Hi Laura,

I still go the same message (even a few seconds ago). Seems that this happens more often when the "&reply filter" string  is appended at the end of the adress (as in http://forums.ni.com/ni/board?board.id=170&reply_filter). But I also get the message when connecting with my logging name...

Another concern is the fact that I can't attach vis to my reply. I have to use zipped file. I had a similar problem long ago. At that time, it was related to the size of the attachment, in relation with a network timeout. 

[Laura F.]

Hi CC,

I'd like to get as much information about the issue you are seeing - does it seem to happen only when you are using the reply filters or are logging in?  Are you using safari or Firefox?

Do you get an error message when trying to attach a vi?  I believe this is working for most people right now so I can't understand what may be happening for you. 

Thanks!

Laura

[muks]

I am able to log on only using ie7 and By any other browser i am not bale to.