anyone have an idea how to make the uVision screen show the directory/version/... you are working from on a permanent basis.
I am working on several versions of the same project, sometimes making a quick check in an older version, sometimes working in the release file, sometimes .....
Till now I have avoided working in the wrong version, but I can easily see that happening some day.
it would be great to see e.g. "ver 1.0" somewhere
Erik
get some paper write "ver 1.0" on it and stick it on your screen with superglue.
simple.
I make sure all "quick checks" are done with "less" or similar tools outside the IDE. Until Keil can explicitly color-code the background for all files not part of the project, it would just be too dangerous to have some outside files open in the Keil IDE. Showing version in the title bar would just not be visible enough to avoid the risk of a mixup.
In short - the Keil IDE isn't allowed to open any files from other projects or from other checkouts.
If I stuck it on with superglue I cold not remove it when I brought up another version :)
anyhow it would not work, often I have 3 versions open at the same time.
the Keil IDE isn't allowed to open any files from other projects or from other checkouts.
not the issue
say I have ver 1.0, 1.04, 1.3 of the same project all open and thus 3 uVisions on the taskbar.
with the current state of uvision I have found no way but memory to know which is 1.0
Yes it is the issue. I don't allow one uVision window to mix files. And I don't allow my desktop to mix uVisions. Any reference viewing is outside uVision to make it 100% obvious that it is not "the" project. That is the only solution that can give so big visual feedback that I can't miss it. I often use a completely different editor - like the free Crimson editor, if I want color coding etc but want to know that I'm not playing with a work object.
And it really isn't much use for having multiple project versions open - I'm much more helped by two-part or three-part diff if I really do need to compare contents between generations of same project. Most source code repository front-ends should have good functionality for this, allowing you to match current directory tree (working project) with specific tagged versions (or maybe from specific time point).
Just a question - why three versions? "work", repository "head" and a repository branch or release?
Work+head+branch is the reason for all the nice three-way diff programs out there, so you can examine the code changes before deciding what to merge between two branches or between branch and head.
sometimes I have to make changes to one particular version (long explanation that I'll skip) and that, often, involves 'stealing'
so, to fix 1.0 I 'steal' some from 1.04, some form 1.13. to do that I have all 3 open. Now a request comes in for something completely different (of course, with "change priority") to be done to a curreent (1.13) function that has not changed in ages and the risk I see is that I may add that code to one of the other versions because I am 'blind' to what version is what tab on the taskbar.
Anyhow, please stop discussing the need, I DO need to have many versions open on occasion and let us come back to "can you make the version or directory visible in the uVision window".
OK, here is the loooooooooooooooooooong explanation
I am making a software backwards compatible for about 2000 values that are user configurable, To check that I need to build and run older versions. I can not just run a .hex of those, because, in some cases, the data left over from another version does not get changed, thus I have to force the older version (say 1.0) to default, for which there is no command, in order to do that I must build, flash download, breakpoint, modify some storage, change variable value, run, save, check. then, to save a lot of downloads, I do the same with another version (say 1.04) and again to force the older version (say 1.04) to default, for which there is no command, again, seeting build, flash download, breakpoint, modifying some storage, changing varibale version, run, save, check. Now I go to the commandline tab for the current version and again build, flash download and see tge progression of the particular values I, at that time are working with filter into the current version.
Happy now?
Erik; A "dirty" method would be to have a multi-project workspace (multiple workspaces) and then set the editor background color for each project to a different color. The main trouble is my age, I could not remember which color went with which project. Also, I work with multiple monitors and open a different Keil on each monitor. Bradford
The main trouble is my age, I could not remember which color went with which project. same problem for same reason :) Also, I work with multiple monitors and open a different Keil on each monitor. well since, for me, runnig debug involves 2 monitors, I would need 6, I do not think there is place on my desk for that
There are nice monitor stands for 6 monitors in a 3x2 configuration. And standard VESA-compatible monitors can be used.