C++ Builder IDE >> Smaller (mostly IDE) proposals for BDS2006 (Final)

by MR » Wed, 21 Dec 2005 15:16:18 GMT

First of all I have to say, I like BDS2006, a major update for BCB5 I
used before, already very much, even if I just explored a minor part
of it.

I'm not sure, if this is the correct place, but since most proposals
concerning the ide-handling I post it here. (Is there a better group?)

Nevertheless I just stumbled about some smaller things I have hoped to
be changed and could be (probably) changed with minor effort:

(1) If a message-box is beeing opend (e.g. while compiling or a
message, that the string to be searched is not available) it is always
opend in the center of the screen. I would have preferred it to be
opened in the center of the BDS-Application. The reason is, that if
you have a virtual screen, i.e. a screen which is larger than the
ability of the monitor to show it, this messagebox is hidden and you
have to scroll the screen to find it.

(2) When searching for a whole word and you enter something like
'FormShow(' this string is searched but could not be found. So an
error should be useful, that 'FormShow(' is nothing which can be found
as whole world.

(3) If nested commentaries are enabled it would be nice the editor
would display the complete commentary-block as commentary. E.g. in
/* a /* b */ c */
the last chars
c */
would not be shown as commentary.

(4) When debugging the color of the execution position should have
priority over the color of an active breakpoint. I.e. if the debugger
holds on an active breakpoint the color of this line should change to
the execution position.

(5) Also I would have liked if the automatically created
events-functions (i.e. the function-frame appearing when one clicks on
e.g. OnClick() in the object-inspector) would have been customizable.
My preferences e.g. would be that the complete function-header
(including the '{' would be in one line (no line-breaks after ~80
chars).

Perhaps is the one or other proposal already implemented and I just
didn't find the option where to adjust it?

Thanks,

Michael


C++ Builder IDE >> Smaller (mostly IDE) proposals for BDS2006 (Final)

by Remy Lebeau (TeamB) » Wed, 21 Dec 2005 15:32:37 GMT






Feature requests should be posted to QualityCentral ( http://qc.borland.com ).
Post one feature per report.


Gambit





C++ Builder IDE >> Smaller (mostly IDE) proposals for BDS2006 (Final)

by Adam Markowitz [Borland] » Wed, 21 Dec 2005 15:39:00 GMT

Michael,
Please add these as separate entries into QC ( http://qc.borland.com ) so we
can track the issues and look at any suggestions for future releases.

Thanks!,
-Adam



<<snip>>




Similar Threads

1. Proposal for declaring methods final (not to be overridden)

2. IDE Proposal: Using unregistered components

3. bds2006 ide project linking woes

A bds2006 project fetched from source control and opened in IDE builds and 
links on machine A without error.

Same project fetched from source control on machine B opened in IDE, when 
asked compiles everything, but consistently fails to link with several 
unresolved items.

Command lines turned on for IDE on machine B.

IDE reported command line for linking on machine B copied and executed in an 
appropriate command line environment, links without error.  (Necessary to 
remove -GA items from the copied command-line - they apparently redirect 
project items to temporary files that are used to store current state of 
possibly edited items open in the IDE.)

Any ideas why the in-IDE linking is consistently failing on machine B, when 
it seems fine on machine B from a command prompt, and fine on machine A 
within the IDE?

Any suggestions of how to get around this (with B/CG provided 
items/features)?  (I'm aware of the alternative linker, but would prefer a 
solution involving B/CG provided tools.)

An attempt to use the ilink32.exe from CB2007 trial did not make any 
difference, still get same errors from IDE link attempt.  (Don't know if the 
standalone executable is actually referenced from the IDE, but we thought 
we'd try it.)

Machine B (4GB memory)
Machine A (2GB memory)

Both have bds2006, update2, hotfixed (I think through 12)


4. Turbo/BDS2006 XP IDE Theme helper

5. BDS2006 small team pack

6. order BDS2006 Pro upgrade small team pack

7. Small BCB5 to BDS2006 Conversion Problem.

I have a component that I bought several years ago.  It was for BCB5, it 
works great and I have used it in a lot of apps.  I am now moving to 
BDS2006 and the original author has "moved on".  I contacted him and he 
is not interested in making his component compatible, but he was nice 
enough to send me the source.

I have gotten it to compile and install under BDS2006 and it works, but I 
had to comment out the registration of the property editors.  Now I would 
really like to see if I can get that working too and I am hoping someone 
here can help.

The problem code looks like this:

namespace EZcomm
{
  void __fastcall PACKAGE Register()
  {
    TComponentClass classes[1] = {__classid(TEZComm)};
    RegisterComponents("EZComm", classes, 0);
    RegisterPropertyEditor(__typeinfo(TEZComm),
                           __classid(TEZComm),
                           "DataBits",
                           __classid(TStringProperty));

    RegisterPropertyEditor(__typeinfo(TEZComm),
                           __classid(TEZComm),
                           "BaudRate",
                           __classid(TIntegerProperty));
  }
}

The error I get is:

[Linker Error] Error: Unresolved external 
'Designeditors::TStringProperty::' referenced from C:\EZcomm\DEBUG_BUILD
\EZCOMM.OBJ

and the same thing for the TIntegerProperty.

I am not a real component writer and the docs are not very good but I am 
hoping it is something simple.

If I comment out the 2 RegisterPropertyEditor statements everything works 
fine.

8. Problem with JB 2005 IDE, very small fonts - JBuilder IDE