File always store in Unix format (CR only) when "Strip Trailing Space" = TRUE

[Silver]

File always store in Unix format (CR only) when "Strip Trailing Space" = TRUE.

SlickEdit Preference:
- Language C/C++ / File Options / Strip Trailing Spaces = TRUE
- File Option / Save / Line Format = DOS

Step:
- Open a C file that have DOS format (LFCR) end of line format.
- Perform an edit on the file.
- Store the file
  -> The file end of line format is UNIX (CR only).

[Ryan]

Thanks for the report.  Looks like "Strip trailing spaces" isn't paying attention to the Line Format option...it seems to be working fine when "Strip trailing spaces" is off.  I have filed a defect and we will get this fixed for the next release.

- Ryan

[hs2]

So is there another v14 release planned ?
HS2

[Silver]

Is there any plan for another release of the actual product with bug fixes for Eclipse 3.5?

[Ryan]

Sorry...I missed this before.

@hs2: There is not another v14 release planned.  The problem Silver is reporting does not exist in standalone SlickEdit.

@Silver: At the moment, we do not have another 3.5.x release planned.  If it is warranted, we will do one...but as of now our next release is scheduled to be with the Eclipse 3.6.0 timeframe.  It still could happen, though.

- Ryan

[wsappington]

I was going to post up a separate topic on the release question (and maybe there has been one but I haven't been here in a long time) but since the question has been raised here, I'll asktoo.

Is this going to be the support model for the Core product going forward - one release per year with hot fixes through the forums and tech support desk?  There are several really annoying issues I've been just putting up with since installing 3.4, like Core tripping over the config environment variables for the standalone product, but I figured I'd wait for a point release since I had already raised that issue with tech support.  But from what I read here, there aren't going to be any point releases, just hot fixes for specific issues.  Is that the plan?

[Ryan]

We don't plan a point release each year for Core, it is only if another release is deemed necessary.  The hotfix mechanism for standalone SlickEdit is not integrated into Core, so we do all the standard Slick-C hotfixes through either support or these forums.

I'll have to check with support about your case with the environment variables.  I don't recall this, but maybe it was shown to me by support some time ago (I looked through your posts and didn't see anything about this).  I also don't see anything filed in Bugzilla.  FYI, VSECLIPSECONFIG is the environment variable you should be setting to specify the location of your Core config.

Are there other outstanding issues which haven't been resolved?  I'd be happy to investigate them.  Have you brought them up here or with support?

- Ryan

UPDATE:  Ok I got the e-mail thread from support about the use of environment variables.  Was this not resolved?  From reading the thread it seems that the only thing which remained unresolved was the fact that location of the metadata folder was not respecting the value of VSECLIPSECONFIG...but we have eliminated the use of this folder as of 3.5.0.  So this should be a non-issue now.  Let me know.

[wsappington]

I'm still using 3.4, wasn't aware that 3.5 was avail, been too busy to check. 

Yeah, still some of the issues I reported with 3.3, to support I think, but I did post some things in the plugin forum.  Clicking the package explorer causes the cursor to jump to the top of whatever file I'm editing, losing the place I was editing (brief emulation), remove trailing spaces on save doesn't always work (I can save a file then execute the command remove-trailing-spaces and find lines that have been modified), couple of others if I think long enough.  When they weren't fixed with 3.4 and there weren't any updates when each time I checked, I kinda just gave up and decided to live with them - path of least resistance.

[Ryan]

Ok, well if you aren't tied to Eclipse 3.4.x I suggest upgrading your IDE to Eclipse 3.5.x and Core 3.5.0.  There were a lot of improvements and new features.

Clicking the package explorer causes the cursor to jump to the top of whatever file I'm editing

That was fixed in 3.5.0.

remove trailing spaces on save doesn't always work

The option in SlickEdit Preferences was never implemented until Core 3.5.0.  As you can see from this thread, there is still an issue with this option in regards to always saving files with only CRs and not LFCRs, even if you have the Line Format set to DOS.

- Ryan