In my windows phone application there are some buttons. I want to change the text according to the devices selected culture Info. I have added the required resource file also made the required changes but still the changes are not reflecting on the UI. Any help will be useful.
Is there any thing that I am missing.
In addition to including the resource files in the project you also need to explicitly specify which cultures you're supporting.
You do this in the project properties. On the "Application" tab there is a list of supported cultures. You must check the box next to the ones you wish to support.
Related
I need to know what (graphically) happens to a button which is assigned to the "disabled" status with a gtk_widget_set_sensitive() function.
I am not the programmer but am documenting the behavior of a tool, built with Gtk+, which buttons are eventually disabled by the programmer by issuing that gtk_widget_set_sensitive() function (I am told). For my documentation, I need to emulate the visual result on the original icon once deactivated but I have no clue on what happens to it. It becomes brighter, blurry? desaturated? other?
Where can I find sources / hints on that?
what follow are caps of the two different (visual) statuses of such a button.
Enabled
Disabled
This is the the documentation from Gtk 1.
Insensitive widgets are “grayed out” and the user can’t interact with them. Insensitive widgets are known as “inactive”, “disabled”, or “ghosted” in some other toolkits.
How does disabled widget look like depends on the theme being used. You can install custom themes in Gnome desktop. I have two screenshot taken with "adwaita" and "adwaita-dark" theme.
Themes can be defined with CSS file. This is repo for adwaita theme. https://github.com/GNOME/gtk/tree/master/gtk/theme/Adwaita. You can search button, insensitive and disabled to find out what colors are being used.
To find the exact color used, you can find it
https://developer.gnome.org/gtk3/stable/GtkWidget.html#gtk-widget-set-sensitive
My project after the build up it displays this
(I am sorry, I can not upload by image tab)
http://www.mediafire.com/download/x7jb77osu8vq6xz/2.png
Previously I had been running successfully, but now the label can not be displayed?
I haven't yet checked your code, (which you can paste it here instead of linking to mediafire). Most probable cause can be that you didn't specify the z-order of label. You need to specify the z-order while adding anything to layer (sprite, label, menu etc etc). This is actually a bug in 3.0 I reported that on forums, not sure if it's fixed in latest version.
Formerly it was possible in iOS to use the hook instagram://camera?caption=YourCaptionHere (from Mobile Safari, or elsewhere) to have the Instagram app open in camera mode with a pre-filled caption. However, that no longer seems to be the case as my previously working URL (hook) no longer populates a caption (though it does still open Instagram in camera mode).
I'm having trouble finding any current information on this, though the caption query string variable seems to have never been documented in the first place.
Does anyone know if this feature is still available under a different query string variable?
To be more clear, I have a link on a web page that attempts to open Instagram in camera mode with a caption. I have a JavaScript click event that checks after 500ms to see if the page is still open, then alerts the user to download the app if the link didn't work:
Open Instagram
Instagram provides documentation on iOS hooks. That documentation does not make any mention of a caption parameter, except sharing a photo via Obj-C (in which they call it annotation). Given the different naming, you could try instagram://camera?annotation=YourCaptionHere and it might even work, but this doesn't seem to be an officially-supported use case.
Further, to support your second paragraph, searching through the history of the docs on the wayback machine doesn't turn up any mention that caption was ever a supported argument... like you said. Interestingly, one of their co-founders claimed this was available 2 years ago... I guess they never made it official, then removed it?
I'm looking to build a chrome extension that allows the user to have an independent subwindow that is the same in each tab (for example you are taking notes and the notes are synchronized among each tab). Also, clicking a link should not destroy this subwindow.
One solution is to inject an iframe in each tab, and try to synchronize this data serverside and send back to each client tab, as it is updated.
This seems very tedious, plus the iframe would be provided by a third party, and I want to make it the easiest for them.
Is there a way I can have a shared dom piece and display it in its current state across several tabs?
There's an API (still experimental as of Chrome 17) that does more or less exactly what you want. If you visit about:flags, and enable "Panels" (they're enabled by default in Dev and on Canary (and on ChromeOS)), you'll be able to use chrome.windows.create with a type of panel to create a floating pane that exists independently from the browser window. That would likely meet your need.
Take a look at the Google Talk extension for an example of how it might work.
I am using Adobe AIR's html control in my desktop application to let users see web pages. I am using the html.historyBack() and html.historyNext() methods to allow moving back and forth. But I want to clear the history once a specific option is selected, say a click on a button, without restarting the application. I tested both versions of AIR, 1.5.2 and AIR 2.0 Beta but unable to find any way to do so.
Is there any way to fix this problem?
Looking forward to hear from you,
Alex Fisherr
I don't think you can direct modify the history object because it's read-only. The easiest way to clear your history is to create a new HtmlLoader and replace the existing HtmlLoader.
This new HtmlLoader will have no history as desired.
If all you want to do is set the enabled state of the back and forward buttons then have a start point int, which you can reset when needed. Then base the history.length on this.