What is the issue with CFBuilder?
I am trying to Check out a file from SS/CFBuilder and all i get is the message
80020009: Network not found.[src=SourceSafe,guid=null]
In fact even perfectly working files that are months old,suddenly become "removed from SS".As a result of which I have only "Team/Commit Changes" option for a given file.The "Team/CheckIn ..CheckOut" options are blanked out.
Also when I am trying to click the "Show Local History",for an pretty old/often used file, it throws an message
No local History available for selected resource!
The Same message is coming for each and every file.
Please help.
Vas
The issue is likely in Eclipse. Eclipse allows you to store local history for the files that have a size lower than 1 MB.
Goto Window >Preferences >General >Workspace >Local History
Increase the Maximum file size so that it is higher than the size of your files.
After applying the change, the next time the file is saved, Eclipse will create a history.
Related
I am trying to modify a program that was contracted by my company before I came to work there. The program uses a .csv file to contain the product numbers and values based on the product number. It seemed simple enough to remove the old file from the current project, and replace the old file with the new file of the same name. I changed the values in 1 record to make the update to pricing. There were no other changes.
After I deleted the old file by highlighting the file in the project, select delete and then select move to trash. I bring the new file in by dragging and dropping from finder. When the Choose options for adding these files comes up, I make sure the check box copy items if needed is checked. I also ensure that Added folders has the option button Create folder references is selected. Add to targets has my project name and is checked. Then I select finish.
When I try to run the program, I get an index out of range error.
While debugging I found that the columns loaded from the file look like this.
["DDN080120000MG35", "DDN.08.01.20000MG35", "DDN.08.01.20000 HE MG35", "MK28708-2000", "Solid Carbide Drill", "Aluminum", "Internal", "8 X D", "20", "20", "243", "190", "160", "484.00 €", "\"$\t715.60\"\r"]
["\u{1A}"]
The last record of the file doesn't have the ["\u{1A}"] shown just above. I ran the old program in debug and this doesn't appear when I set a breakpoint.
Does ["\u{1A}"] represent an EOF marker that shouldn't be there? Am I missing some sort of compile action that I need to take with the file before I load it? I'm lost. Any help would be appreciated.
The issue wasn't with the code. It was with the difference between Windows and IOS system and how they handle files. The numbers program in IOS was attaching a character at the end of the .csv file that already had an EOF marker on it. Xcode was confusing the original EOF marker from an Excel file as a record in the file causing an index out of range error. The answer was to open the original csv file in TextEdit, make the modifications and saving it back as a csv. Once I dropped it into the project, the problem was solved.
How can I discard remote changes in binary files when merging? There is only menu item to discard changes in local file. When I'm trying to "resolve" it tells it can't do that thing for binary file.
Sorry, I've mentioned "resolver" menu but it was "conflict solver". Log http://pastebin.com/xhGuc3du.
Although when I'm using "resolve" I see OK icon in the operations log (right bottom corner) but "conflict" label does not disappear. Log http://pastebin.com/DEDWQSht.
To discard remote changes, Local|Discard should be sufficient. To set your local content either to your own version before the conflict ('ours') or to the remote version ('theirs') use Local|Resolve and select the corresponding option there.
I am running Turbo C on DOSBox in Ubuntu 12.04.
The problem is that two black stripes are coming on either of screen. I want to remove them.
My computer is a Dell Studio 15z with screen resolution 1366x768. I don't have a problem even if distortion occurs.
Relevant part of my dosbox.conf file:
[sdl]
fullscreen=true
fulldouble=false
fullresolution=1366x768
windowresolution=1366x768
output=overlay
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
usescancodes=true
go to dosbox installation directory (on my machine that is C:\Program Files (x86)\DOSBox-0.74 ) as you see the version number is part of the installation directory name.
run "DOSBox 0.74 Options.bat"
the script starts notepad with configuration file: here change
windowresolution=1600x800
output=ddraw
NOTE: Non-windows users will want to use output=opengl instead.
(the resolution can't be changed if output=surface - that's the default).
safe configuration file changes.
For using DOSBox with SDL, you will need to set or change the following:
[sdl]
windowresolution=1280x960
output=opengl
Here is three options to put those settings:
Edit user's default configuration, for example, using vi:
$ dosbox -printconf
/home/USERNAME/.dosbox/dosbox-0.74.conf
$ vi "$(dosbox -printconf)"
$ dosbox
For temporary resize, create a new configuration with the three lines above, say newsize.conf:
$ dosbox -conf newsize.conf
You can use -conf to load multiple configuration and/or with -userconf for default configuration, for example:
$ dosbox -userconf -conf newsize.conf
[snip]
---
CONFIG:Loading primary settings from config file /home/USERNAME/.dosbox/dosbox-0.74.conf
CONFIG:Loading additional settings from config file newsize.conf
[snip]
Create a dosbox.conf under current directory, DOSBox loads it as default.
DOSBox should start up and resize to 1280x960 in this case.
Note that you probably would not get any size you desired, for instance, I set 1280x720 and I got 1152x720.
Here's how to change the dosbox.conf file in Linux to increase the size of the window. I actually DID what follows, so I can say it works (in 32-bit PCLinuxOS fullmontyKDE, anyway). The question's answer is in the .conf file itself.
You find this file in Linux at /home/(username)/.dosbox . In Konqueror or Dolphin, you must first check 'Hidden files' or you won't see the folder. Open it with KWrite superuser or your fav editor.
Save the file with another name like 'dosbox-0.74original.conf' to preserve the original file in case you need to restore it.
Search on 'resolution' and carefully read what the conf file says about changing it. There are essentially two variables: resolution and output. You want to leave fullresolution alone for now. Your question was about WINDOW, not full. So look for windowresolution, see what the comments in conf file say you can do. The best suggestion is to use a bigger-window resolution like 900x800 (which is what I used on a 1366x768 screen), but NOT the actual resolution of your machine (which would make the window fullscreen, and you said you didn't want that). Be specific, replacing the 'windowresolution=original' with 'windowresolution=900x800' or other dimensions. On my screen, that doubled the window size just as it does with the max Font tab in Windows Properties (for the exe file; as you'll see below the ==== marks, 32-bit Windows doesn't need Dosbox).
Then, search on 'output', and as the instruction in the conf file warns, if and only if you have 'hardware scaling', change the default 'output=surface' to something else; he then lists the optional other settings. I changed it to 'output=overlay'. There's one other setting to test: aspect. Search the file for 'aspect', and change the 'false' to 'true' if you want an even bigger window. When I did this, the window took up over half of the screen. With 'false' left alone, I had a somewhat smaller window (I use widescreen monitors, whether laptop or desktop, maybe that's why).
So after you've made the changes, save the file with the original name of dosbox-0.74.conf . Then, type dosbox at the command line or create a Launcher (in KDE, this is a right click on the desktop) with the command dosbox. You still have to go through the mount command (i.e., mount c~ c:\123 if that's the location and file you'll execute). I'm sure there's a way to make a script, but haven't yet learned how to do that.
Looking again at your question, I think I see what's wrong with your conf file. You set:
fullresolution=1366x768
windowresolution=1366x768
That's why you're getting the letterboxing (black on either side). You've essentially told Dosbox that your screen is the same size as your window, but your screen is actually bigger, 1600x900 (or higher) per the Googled specs for that computer. So the 'difference' shows up in black. So you either should change fullresolution to your actual screen resolution, or revert to fullresolution=original default, and only specify the window resolution.
So now I wonder if you really want fullscreen, though your question asks about only a window. For you are getting a window, but you sized it short of your screen, hence the two black stripes (letterboxing). If you really want fullscreen, then you need to specify the actual resolution of your screen. 1366x768 is not big enough.
The next issue is, what's the resolution of the program itself? It won't go past its own resolution. So if the program/game is (natively) say 1280x720 (HD), then your window resolution setting shouldn't be bigger than that (remember, it's fixed not dynamic when you use AxB as windowresolution).
Example: DOS Lotus 123 will only extend eight columns and 20 rows. The bigger the Dosbox, the bigger the text, but not more columns and rows. So setting a higher windowresolution for that, only results in bigger text, not more columns and rows. After that you'll have letterboxing.
Hope this helps you better.
by double-clicking in between the headers of the Eclipse History view (Revision, Tags, etc.) each fields gets resized (enlarged to the right) to accommodate the size of the longest value.
Now, because my Tags columns contains very long values (long strings containing the list of tags) when I double-clicked on the headers between Tags and the next header (Revision Time), the Tags column got enlarged to the right so much that the Revision Time column has disappeared.
I can't find a way to get to the Revision Time column. Scrolling to the right using the horizontal scroll line is useless.
Any idea?
Thank you!
had this happen with eclipse 3.7 on Windows
as per https://bugs.eclipse.org/bugs/show_bug.cgi?id=313480
close Eclipse
delete .metadata/.plugins/org.eclipse.team.cvs.ui/dialog _settings.xml file
start Eclipse
do history and see it work
I have the same. Thanks to Dev.
I found the answer The Author column in the CVS history disappeared from Eclipse
Go to the path $WORKSPACE/.metadata/.plugins/org.eclipse.team.cvs.ui in your filesystem. Where $WORKSPACE is the directory that has your Eclipse workspace.
Edit the file dialog_settings.xml in that directory.
find <item value="put something reasonable here" key="COL_TAGS"/>
With BC2, when i click the Show differences... option in SourceGear Vault. It allow me to copy from the repository to the working version and save but I can't do this with BC3. It doesn't allow copying to the otherside (right) and have the editing disabled showing at the bottom of the BC3. It is even the same with DiffMerge. What am I not understanding here?
Can someone explain to me why the changes in BC3 and is there a workaround?
Beyond Compare will disable editing of a file for any of the following reasons:
It's one of the input files in a 3-way merge
The comparison was cancelled
The comparison encountered an error (corrupt file, invalid character encoding, out of memory, gamma rays, etc)
The file format's conversion settings don't support converting back to the original format (MS Word, PDF)
The file is on a read-only "filesystem" (7zip/RAR/CHM archives, CD/DVD-ROMs)
A file or parent folder had editing explicitly disabled by the user in the session settings or using the /ro command line switches
The viewer itself doesn't support editing (eg, Hex Compare prior to v4)
Also, the Full Edit (F2) toggle in the Text Compare View menu switches between inline editing and line-based mode. If it's disabled you can copy/delete whole lines and type in the line details edits at the bottom of the window, but the main windows won't have a cursor, typing is disabled, and it will always select whole lines. Unlike the above items, this doesn't show "Editing Disabled" in the status bar.
there must be a flag on the command line to call BC such as /ro# or /#ro or /(side)readonly (where side is left or right), it prevents editing.
these flags are there because differs are often called with temporary files to diff, in particular from SCC. and Vault probably has a single "external diff" command, thus you have to choose whether the flags are always there, it protects you from unexpectly editing a temporary file and loose this work when closing the diff tool, or not.
The few reasons I have found are:
If the encoding of the file is different than the default. In this case change the encoding to the expected one. (Japanese-ShiftJIS in my case)
If a refresh of files is in progress.