I have recently installed Expression Blend 4 and created a test Silverlight 4 project.
When I set the main page FlowDirection to RightToLeft the designer won't change the direction but if I run the application it will be displayed correctly.
Is this a bug or do I have to do something?
Thanks.
I believe you were the one who also put the post at the microsoft social site (available here) but since it took me a while to find it, I'll also put the response here:
Unni Ravindranathan - MSFT:
We do not support RTL on the design-surface, so what you are seeing is currently by design (the value that you set is ignored). We hope to be able to support it in the future, however.
Let's hope they would!
Related
We are developing a Windows10 Universal App (UWP). We have huge issues related to how RelativePanel behave depending of syntax and pc.
We have dynamic data response from a web service and we have to display a dynamic structure of UI controls to render the GUI.
We are trying to use RelativePanels with child elements composed of ItemsControls rendering different type of sub data (Addresses, Phones, etc..).
The ItemTemplate of each ItemsControl' item is a Template composed of a RelativePanel.
Now, the weird stuff happened differently between design and runtime.
At design time, when we want to set Target UIElement of the RelativePanel, we can use the following syntax:
Ex: RelativePanel.Below="EntryMobileNumbers" or
Ex: RelativePanel.Below="{Binding ElementName=EntryMobileNumbers}" />
They are supposed to both work but they don't.
For some RelativePanels’ child elements, if we use the first syntax, the xaml designer bugs and display weird error message
about “value must be of type UIElement”.
Looked on forums for this type of Xaml error and it seems for some developers it’s better to use the second syntax with the Binding.
The good side of it is with that the design is not displaying the squigglys and the error BUT the pb is at Run-time;
the result is wrong and some elements are overlapping.
With syntax 2
With syntax 1
We have also different issues between dev pc’s. With the VS2015 Enterprise installed on all pc’s,
some are displaying squigglys or crash the Xaml Designer with Syntax 1 and some are not.
We also tried to update VS2015 with yesterday’s RC1. It fixed the issues on one of the Pc and not on the others.
PS. All samples out there are very simple. I would very happy to see a "real life" application.
Like e.g. Money from the store to see how layout are managed
RelativePanel.Above="{Binding ElementName=SubTitleDesktop}"
instead of
RelativePanel.Above="SubTitleDesktop"
and it will helps you get rid off errors
I am helping a co-worker with a issue in a production datatbase. The database makes use of a visual indicator to show the user during long partial refreshes. We are in the process of upgrading the application to Notes 9.0.1.
The method that is used is described in detail in this blog post by Eric Tomenga: https://www.socialbizug.org/blogs/tomenga/entry/dojo_loading_image_indicator_while_partial_refresh_loads_data?lang=en_us (blog that Eric's references appears to be offline)
The code is not altered from what is shown in the post. Works in 8.5.3 completely, but in 9.0.1, the "Please Wait" works but the spining image is absent.
My suspicion is that newer dojo version that Notes 9 uses changes something that breaks this. Downgrading dojo versions is not an option. Hoping for a workaround.
<xp:this.onStart><![CDATA[XSP.startAjaxLoading()]]></xp:this.onStart>
<xp:this.onComplete><![CDATA[XSP.endAjaxLoading()]]></xp:this.onComplete>
<xp:this.onError><![CDATA[XSP.endAjaxLoading()]]></xp:this.onError>
This is added to the element you want to use it with (button in this case). The following dojo modules are added to XPage resources: extlib.dijit.ExtLib + extlib.dijit.Loading
I'm pretty sure you'll need to add the relevant Dojo module as well. You can see a working example of the code on the Admin page of the XPages Extension Library demo database. I can't remember off-hand which dojo module it is, so please post here if that solves it.
I wan't to create a semi-bold font in VB.NET.
Why isn't semi-bold available in intellisense?
[screenshot]
I am using .NET 4.5.
Label1.Font = New Drawing.Font("Segoe UI Semibold", 10)
Add Semibold to font name.
The answer is simple and is just available in front your eyes.
Just look with care the image you attached and MSDN Document:
System.Drawing.FontStyle is different from System.Windows.FontWeights.
A tip: no big deal, but for conscience' sake and future page visitors, you've cited something about .Net version 4.5... If you click on combo "Other versions", it will show the documentation page in others .Net versions.
So, in this case, System.Windows.FontWeights was introduced by .Net 3.0.
The more correct sentence is: .Net 3.0 (and up) is required to use System.Windows.FontWeights.
System.Drawing.Fonts does not support a SemiBold setting weight. The FontWeights is in the System.Windows namespace which is WPF/Silveright - which does support Semi-Bold. However System.Drawing.Fonts is part of Windows Forms which does not.
WPF and Windows Forms use different rendering engines and are not compatible.
This is one of my biggest turn offs from the newer versions of XCode(ie 4.5+) is the following: in earlier versions.. when you option click a system defined function.. you get a bubble that offers you a link that takes you directly to the function definition in organizer:
but on XCode 4.5 and later.. that changed: the exact link of the function is no longer provided.. instead you can only click on the reference of the entire class!
any idea how that can be changed? Another problem I have is the fact that I just couldn't figure out how to do offline documentation viewing on xcode 4.5 (it worked fine in earlier versions.. and yes i did download all the documentation locally and followed all the SOF links.. but no luck!)..
Make sure you download all the documentation locally via XCode->Preferences. Once it's local there should be no problem accessing specific functions through the popup - it says "Class Reference" but it automatically opens the relevant documentation within the class reference.
After setting up a table model in Qt 4.4 like this:
QSqlTableModel *sqlmodel = new QSqlTableModel();
sqlmodel->setTable("Names");
sqlmodel->setEditStrategy(QSqlTableModel::OnFieldChange);
sqlmodel->select();
sqlmodel->removeColumn(0);
tableView->setModel(sqlmodel);
tableView->show();
the content is displayed properly, but editing is not possible, error:
QSqlQuery::value: not positioned on a valid record
I can confirm that the bug exists exactly as you report it, in Qt 4.5.1, AND that the documentation, e.g. here, still gives a wrong example (i.e. one including the removeColumn call).
As a work-around I've tried to write a slot connected to the beforeUpdate signal, with the idea of checking what's wrong with the QSqlRecord that's about to be updated in the DB and possibly fixing it, but I can't get that to work -- any calls to methods of that record parameter are crashing my toy-app with a BusError.
So I've given up on that idea and switched to what's no doubt the right way to do it (visibility should be determined by the view, not by the model, right?-): lose the removeColumn and in lieu of it call tableView->setColumnHidden(0, true) instead. This way the IDs are hidden and everything works.
So I think we can confirm there's a documentation error and open an issue about it in the Qt tracker, so it can be fixed in the next round of docs, right?
It seems that the cause of this was in line
sqlmodel->removeColumn(0);
After commenting it out, everything work perfectly.
Thus, I'll have to find another way not to show ID's in the table ;-)
EDIT
I've said "it seems", because in the example from "Foundations of Qt development" Johan Thelin also removed the first column. So, it would be nice if someone else also tries this and reports results.
I use Qt 4.6.1 in PyQt and the problem is still here. Removing "removeColumn(0)" solves the issue.