Databases
StackOverflow2013
Postsdbo
POset culture of individual WPF user control
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POset culture of individual WPF user control
    primarykey
    data
    text
    <p>I have written a user control which is not compatible with cultures other than "en-US". Also it is inevitable to embed this user control in an application with a culture which is not "en-US". So is it possible to force the application to not to change this user control's culture? <br>Its preferable to have a solution inside the user control. <br> I have read this thread : <a href="https://stackoverflow.com/questions/374518/localizing-a-winforms-application-with-embedded-wpf-user-controls">Localizing a WinForms Application with Embedded WPF User Controls</a> but I can not use <strong>WpfLocalization.LocalizationScope.SetCulture</strong> <br> Does this function really exists ?</p> <p>And also there is a <strong>Localizable</strong> tag which can be set to <strong>False</strong> but It is just for resource definitions in <strong>.csproj</strong> files: <a href="http://msdn.microsoft.com/en-us/library/ms788718.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms788718.aspx</a></p> <p>So is there anybody who has any idea about this problem ?</p> <p><hr> <strong>More clarification :</strong><br> Suppose we have an application with culture X and a user control which is compatible with culture "en-US". This user control has a dependency property which is of DateTime type and it is getting its value by this way :</p> <pre><code>&lt;my:uc1 x:Name="UserControl1" Date="4234/12/22" /&gt; </code></pre> <p>When application culture is "en-US" user control will get <strong>"4234/12/22"</strong> but when the application culture is something else, it converts <strong>"4234/12/22"</strong> automatically to the application's own calendar and delivers <strong>"0744/04/08"</strong> to the user control and ruins every logic behind the user control ! It's completely a disaster.</p> <p>I want to prevent this conversion by setting the user control's culture exclusively to "en-US".</p> <p>Hope that I have clarified the situation enough.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USSpongebob Comrade
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POset culture of individual WPF user control
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POset culture of individual WPF user control
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBesides the surprising date you want to use (which by the way isn't represented in "en-US" format which is `M/d/yyyy`) which culture converts it to "0744/04/08" (even more surprising)?
      singulars
      1. POset culture of individual WPF user control
      1. USMartin Liversage
    2. CO@Martin Liversage: It's just an example. Let me keep that culture clandestine :-&
      singulars
      1. POset culture of individual WPF user control
      1. USSpongebob Comrade
    3. COSorry if I disclose any secret, but given the huge year I'd say Hebraic calendar... More seriously, this thread is really interesting to me as I'll probably have to manage soon dual-culture (French/Arabic language or Gregorian/Ethiopian calendar) oddities.
      singulars
      1. POset culture of individual WPF user control
      1. USodalet
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload