I just updated my project from gtkmm 2.4 where I would add a toolbar and change it to vertical via:
toolbar.set_orientation();
In gtkmm 3.2 this function doesn't exist and I couldn't find anything about it on the "Changes in gtkmm 3.0" page. I tried placing it in a VBox but Gtk::Toolbar doesn't inherit from Gtk::Orientable so I think perhaps gtk has removed this functionality? Is there a way to get the old behaviour?
With Gtkmm 3.4 i can do (the documentation of Gtk 3.2 confirms) :
myToolbar->set_property("orientation", Gtk::ORIENTATION_VERTICAL);
see gtk/gtktoolbar.c (near line 497: g_object_class_override_property(..., "orientation"))
However, the text of icons appears now. To remove:
myToolbar->set_property("toolbar-style", Gtk::TOOLBAR_ICONS);
see gtk_toolbar_set_style
Hoping that this can help you.
There is no direct method to change the orientation, but there is a property you can set:
toolbar.property_orientation().set_value(Gtk::ORIENTATION_VERTICAL);
Or
toolbar.property_orientation() = Gtk::ORIENTATION_VERTICAL;
Related
How do i fix or ignore this warning popup? The example works fine, but this warning popup keeps showing. I looked around for a solution and image magic seems to be the fix. However, there are no images causing this problem in the sample code. I'm assuming it is what is being loaded by the browser. Can someone help me solve this problem please?
I can confirm this issue with wx.version=3.0.2.0 msw (classic) and cefpython 31.2. The navigation bar in this example loads three buttons (back, forward, reload) from this directory: c:\Python27\Lib\site-packages\cefpython3\wx\images:
Arrow Left.png
Arrow Right.png
Button Load.png
These cause the "iCCP: known incorrect sRGB profile" error.
Solution: In the c:\Python27\Lib\site-packages\cefpython3\examples\wx\ directory there are three images (back.png, forward.png, reload_page.png). Replace the problematic images with these by renaming them (back.png to Arrow Left.png etc) and copying to the c:\Python27\Lib\site-packages\cefpython3\wx\images directory.
Created Issue #221 to fix this.
If using wx 2.9/3.x you might also encounter text input issue. The cefpython 31.2 release was tested with wx 2.8 only.
I'm using IntelliJ IDEA v12. When I import a project, there’s a strikeout/strikethrough line on the method which has the annotation #Deprecated, but I used alt+enter to disable it. So, how can I reactivate this feature? I want to display that strikethrough, thanks!
Open Settings -> Type Inspections to go to inspection settings -> Type Deprecated to find out all deprecated related inspection settings -> Check Deprecated API usage.
IntelliJ had a bug in 2018.3, 2018.2.2 (182.4129.33). It was fixed in builds 191.65, 183.3691.
Setting -Dide.text.effect.new.metrics=false in the .vmoptions fixes the problem.
In addition to Ionghua's answer .....
If you find that IntelliJ is still not striking out deprecated methods, even though you have enabled the inspection as above, check to make sure that your code is not ignoring deprecation warnings with #SuppressWarnings("deprecation").
In addition to longhua's answer... and vegemite4me...
Another possible source for this problem might be custom color themes.
If you are using a custom theme, make sure that it contains strikethrough. I was using monokai-sublime and there is no strikethrough for #Deprecated annotations. When I changed the color theme from monokai to darcula strikethrough worked as expected.
I found that the only thing that worked for me with version 2019.2 192.5728.98, runtime 11.0.3+12-b304.10 was to use Help | Edit VM Options and add -Dide.text.effect.new.metrics=false
I have been developed one application in extjs 4.0.7. and now if i want to use extjs 4.1. for further implementation of that application.
Is it possible? Plz help me, if answer is yes.
Thank you
Of course an upgrade is possible. Replace your extjs scripts (ext-all.js etc) from 4.0.7 to 4.1. In most cases you should not face any problem as this is mostly a performance focussed release. http://www.sencha.com/blog/whats-new-in-ext-js-4-1
Convert from Extjs 4.0.7 to Extjs 4.1.
Yes you can upgrade your application from extjs 4.0.7 to 4.1.1 For that you need to replace your ext-all.js/ext-debug-all.js (for debug purpose) but after replacing you may get few problems related to syntax such as in editor, previously we were using record, instead of that we need to use e.record.
listeners : {
'edit' : function(editor, e) {
var grid = e.grid;
var record = e.record;
}
}
There are some issues with the ext-all.css if you are using any custom images on the panel header. Be wary of it. And also html property in the panel is not working.
I'm re-creating an AIR app with FB 4.5.1. (I've started from scratch, having had trouble importing FB 4 projects).
In the app.xml I have the following defined:
<systemChrome>none</systemChrome>
<transparent>true</transparent>
Having done this I still get a full window with titlebar, min, max, and close buttons.
what gives?
I believe you need to create a skin for the application.
This appears in Adobe's forum, and includes an FXP of a functional transparent app:
http://forums.adobe.com/thread/476699
Setting systemChrome & transparency along with "backgroundAlpha" to "0" would have helped in Flex 3.
But, skinning of components in Flex 4 i.e Spark components is little different and completely customizable.
Following are the steps you need to do make the window transparent.
Set systemChrome to "none" in the XML configuration file
Set transparent to "true" in the XML configuration file
Copy the skin code from <SDK_FOLDER>\frameworks\projects\airframework\src\spark\skins\spark\S parkChromeWindowedApplicationSkin.mxml and paste in a new MXML file.
Set the "alpha" property of "backgroundRect" object inside the skin file to "0".
Assign the newly created skin as the "skinClass" for "s:WindowedApplication" object
Please import the attached FXP file using "File->Import Flex Project" menu and have a look at the code to make it much more clear.
First, I discovered it is easier to interact with app.XML by opening it via "Open With -> Text Editor".
Second, and this is really embarrassing, I had simply failed to remove the comments bracketing
was:
<!-- <systemChrome>none</systemChrome> -->
<!--<transparent>true</transparent>-->
should have been:
<systemChrome>none</systemChrome>
<transparent>true</transparent>
...duh! I knew better, but...
Lastly, for a completely chromeless app, add
showStatusBar="false"
to the app header.
that's it!
I have tried both Titanium.UI.RETURNKEY_DEFAULT and Titanium.UI.RETURNKEY_NEXT,
but neither will add a new line in the text area. Titanium.UI.RETURNKEY_DEFAULT just closes the keyboard.
I see that there was a related bug report here -
http://jira.appcelerator.org/browse/TIMOB-470?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#issue-tabs
It is marked as fixed, but doesn't seem to have been added to the release I'm working with.
Does anyone have a work around for this?
Thanks!!
Try to add this property to your TextArea:
suppressReturn: false
I tested this with iPhone and can confirm that it works.