Click here to Skip to main content
15,887,746 members
Home / Discussions / C#
   

C#

 
AnswerRe: C# - least square method Pin
Pete O'Hanlon24-Dec-18 8:51
mvePete O'Hanlon24-Dec-18 8:51 
GeneralRe: C# - least square method Pin
Member 1409938024-Dec-18 9:27
Member 1409938024-Dec-18 9:27 
GeneralRe: C# - least square method Pin
Dave Kreskowiak24-Dec-18 11:22
mveDave Kreskowiak24-Dec-18 11:22 
AnswerRe: C# - least square method Pin
OriginalGriff24-Dec-18 19:42
mveOriginalGriff24-Dec-18 19:42 
QuestionWhy this change language in multilingual need twice click ? Pin
@Sai_Y23-Dec-18 17:29
@Sai_Y23-Dec-18 17:29 
AnswerRe: Why this change language in multilingual need twice click ? Pin
OriginalGriff23-Dec-18 20:13
mveOriginalGriff23-Dec-18 20:13 
QuestionRe: Why this change language in multilingual need twice click ? Pin
Eddy Vluggen23-Dec-18 21:10
professionalEddy Vluggen23-Dec-18 21:10 
Questionconstraining an ExtenderProvider ... Winform Component Pin
BillWoodruff22-Dec-18 6:48
professionalBillWoodruff22-Dec-18 6:48 
My intention is to publish, here, a tutorial on extending 'Form with a Component in what I hope will be a novel, and useful, way.

As you may know, a component that implements IExtenderProvider (see: [^]) can be drag-dropped into the component UI area of the Form, and will be exposed at design-time by the type of object it extends.

Note that the MSDN sample implementation here: [^] ... as so often, brain-damaged with crap code ... is a Control, not a Component.

Okay, now I have my Component working, extending 'Form; I have solved the problem of detecting the Component instance's run-time Container using reflection (the only way to do it !). Necessary Properties are now exposed in the design-time 'PropertyGrid. Depending on the user's design-time choice, one of four possible "flavors" of another Form are created.

All this is working. The issue now ... is that I want to constrain the number of auxiliary Forms created to only one of each of the four "flavors." AFAIK, this cannot occur at design-time in the Component's code: there aren't any Events, and the 'InitializeComponent method does not get called.

So, which do you think is better: handle preventing duplicates in a special static Class, or handle them in the Form 'Load Event when I enumerate the Components, and take actio based on the user-set Properties ?

thanks, Bill
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot

AnswerRe: constraining an ExtenderProvider ... Winform Component Pin
Gerry Schmitz23-Dec-18 8:30
mveGerry Schmitz23-Dec-18 8:30 
GeneralRe: constraining an ExtenderProvider ... Winform Component Pin
BillWoodruff23-Dec-18 12:06
professionalBillWoodruff23-Dec-18 12:06 
QuestionProperties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 20:05
_Q12_21-Dec-18 20:05 
AnswerRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 21:00
mveOriginalGriff21-Dec-18 21:00 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 21:29
_Q12_21-Dec-18 21:29 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 21:42
mveOriginalGriff21-Dec-18 21:42 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 21:48
_Q12_21-Dec-18 21:48 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 21:50
mveOriginalGriff21-Dec-18 21:50 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 22:01
_Q12_21-Dec-18 22:01 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 22:20
mveOriginalGriff21-Dec-18 22:20 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 22:37
_Q12_21-Dec-18 22:37 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 23:08
mveOriginalGriff21-Dec-18 23:08 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 22:33
mveOriginalGriff21-Dec-18 22:33 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 22:47
_Q12_21-Dec-18 22:47 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 23:04
mveOriginalGriff21-Dec-18 23:04 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
_Q12_21-Dec-18 23:09
_Q12_21-Dec-18 23:09 
GeneralRe: Properties does not change in custom MouseEnter event incomplete implementation. Pin
OriginalGriff21-Dec-18 23:14
mveOriginalGriff21-Dec-18 23:14 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.