I'm working with the pageframe control in VFP 9.0 with a bunch of tabs. I'm trying to achieve multi-lines caption in each tab as in the following screen, but I don't know how to do.
I tried these, but no luck.
.Caption = 'Watch 1' + chr(13)+chr(10) + '(00~04)'
.Caption = 'Watch 1' + chr(13)+ '(00~04)'
Without some fancy advanced smoke-and-mirrors going on, VFP does not do multi-line tab text within pageframe controls... And I've been using VFP since vs VFP3 back about 1993 when it was first released.
As for your "Acceptance Rate" of zero %. This help forum appreciates feedback to know when a question is resolved so those looking for similar questions know which answer "fixed" the problem originally asked instead of guessing which one eventually worked. I would suggest going back to your other questions and seeing if any such answers HAVE helped, and if so, click the check mark to the left of the answer indicating it is resolved.
Related
This question already has answers here:
Some Emmet abbreviations in VSC not working, like '!' or using '*'
(8 answers)
Closed 7 months ago.
I have started to use Visual Studio Code and am having issue's with Emmet.
When I type in the code ul>li and hit tab to expand, it expands. But when I try to multiply the code like ul>li*3, it does not expand and I get no suggestion for that abbreviation. I have added "emmet.triggerExpansionOnTab": true to the json file, and that did nothing, and I have restarted all extensions with the restart extension host command.
All suggestions on how to fix this issue are appreciated.
Yes, I am facing this issue too since latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
After checking the box You can see the suggestion and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.
You can get them back consistently by turning Inline Suggest on.
If you find that annoying or distracting, you can leave that off and use ctrl+space to get the old popup shortcut to come up, and then hit tab as normal.
As highlighted by the screenshots above, the regex checkbox of PhpStorm's find window is no longer visible by default. This is annoying, because I cannot always see, whether a regular expression is narrowing my search or not. I already googled for a solution, but I cannot seem to find one.
Does anybody of you know how to "fix" this?
Thanks a lot in advance :)
Edit: In case you need to know, I am working on a Mac.
It's a bug in 2018.1.
https://youtrack.jetbrains.com/issue/IDEA-188790 -- ticket status says fixed ... but target version is only 2018.2.
Try asking there if the fix will be included in 2018.1.3 or so .. or will it be in 2018.2 only.
This is the first time I am trying to contribute to Mozilla. I went through several articles and documentation/resources to get a hang of what could be the best first steps to get started. I started off from this page http://whatcanidoformozilla.org1 and chose to start off with Java.
On initial tinkering I was taken to https://wiki.mozilla.org/Mobile/Get_Involved and eventually https://wiki.mozilla.org/Mobile/Fennec/Android/Suggested_workflow resource suggested that the best way to get started with it would be to pick up some simple bug and propose a patch for it.
So then I went to http://www.joshmatthews.net/bugsahoy/?java=1&simple=1 and this specific bug drew my attention. The description of the bug mentioned this :
There are some methods that we share (or can share) across our DB
implementations, like appending PARAM_SHOW_DELETED, PARAM_LIMIT, or
PARAM_PROFILE.
These are currently spread across LocalBrowserDB, TabsAccessor,
URLMetadata, and so on. It'd be nice to clean these up.
Question 1. Now how do I get some more context on what exactly is the bug and what is required to be done ?
As of now there seems to be 2 patches already submitted from what I understood (and please correct if my understanding is wrong here). So to get some context about the bug I went ahead and opened up the first patch submitted here.
It gave me some idea as to at least where exactly is the code itself that needs to be fixed. And I found it here
Question 2. Am I on the right track on how to figure out the code that needs to be fixed ?
Question 3. Even after reaching the DBUtils.java file I could not find any documentation about what the class basically does, or where does it fit into the whole picture. Could someone please help me with this, as to how do I figure out what a class is supposed to be doing etc. or at least some documentation around it?
You're on the right path. Basically, the What Can I Do For Mozilla website is a quick and easy way to let you discover projects you might be interested in, so it's the first gateway to the coding contributions.
That said, you did good in picking a bug to start off. However, as you saw the bug was already being worked on by somebody else (marked as Assigned). Your best bet is to find some new "good first bug" to work on. This might be a complicated task, as Bug's Ahoy shows only a few not owned good first bugs.
You should try to get in touch with the Fennec team, either via email or IRC (the latter for quicker responses).
Now, to answer your questions, in a more general way
Question 1. Now how do I get some more context on what exactly is the
bug and what is required to be done ?
Usually, this should be described in the first comment in the bug, on Bugzilla. If that's not the case, feel free to drop a message there and ask for more directions. You can also flag the reporter or the mentor of the bug using the needinfo functionality, as they are usually better shown.
As you can see, somebody asked for more info in comment 1 and some new directions were given.
In general, you won't find a patch with code on the bug itself, but you might find links to files and more precise directions on what to change and how. If not, again, feel free to ping the reporter and/or mentor.
Question 2. Am I on the right track on how to figure out the code that
needs to be fixed ?
You're on the right path. In general, if there are no links to files or DXR on the bug, but some code is mentioned, you can look it up using DXR, as you did.
Question 3. Even after reaching the DBUtils.java file I could not find
any documentation about what the class basically does, or where does
it fit into the whole picture. Could someone please help me with this,
as to how do I figure out what a class is supposed to be doing etc. or
at least some documentation around it?
What I usually do when navigating the Firefox code and need some more background on a not so well documented class, is browse the change log for that file, clicking on the Log button in the top-right panel on DXR (when displaying the file). It will show you a list of bugs that affected the file. You can even trace back the original file that implemented it, to get more context.
On the other hand, if you're only interested to the history of a single line of code within a file, then the blame tool is your friend. It tells you who last touched the line, the changeset and the related bug number. That is also accessible from where you can find the Log, here.
In the case of DBUtils.java, however, it looks like the class just holds some utility functions for database access.
To see how something is being used within the Firefox codebase, you can still use DXR. Here's a sample search for the DBUtils object.
Can anyone help me solve my problem in AS3?
(P.S I wanted to have a clear button that will minimize the time spent in using this simple calculator :) )
Welcome to StackOverflow, crazywaltz. Just so you know, you need a lot more detail in your question from now on - platform, goal, current relevant code (what have you tried?). Put info mostly in your question, not in your title.
You also need to do your own research in the future. Google is a great resource! The documentation for AS3 is also available online, so read that. You could have found your answer in just a few minutes that way. People on StackOverflow do not like answering questions like this, and you won't get good answers usually.
That said, I'll help you out this first time. The code to clear a text field is as follows. I'm assuming your clear button is called btnClear, and your text box is called myTextField.
btnClear.addEventListener(MouseEvent.CLICK, clearText);
function clearText(evt:MouseEvent)
{
myTextField.text = "";
}
It is up to you to find out how this code works, and how to add buttons and text fields to your stage.
I cannot figure out how to get the HTML elements to wrap lines in Chrome dev tools. I'm working with some long and complicated SVG paths and I hate scrolling horizontally to check the other element attributes. Word wrap is checked under the settings area in chrome dev tools. Suggestions?
Looks like there is no Word Wrap available for now :( and seems like people have been asking forever, I just posted my vote for word wrap too
https://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=73193
Edit: looks like it is a feature by default now (click on the three dots on the top right, then click on Settings):
This is quite an old thread, but unfortunately still relevant.
Word wrap only works in the Elements panel. From the documentation:
As with any text editor you can choose to wrap long lines of code in the Elements panel.
The link in Leon's answer actually refers to the Network panel, although several of the comments suggest that others are also looking at this more generally; e.g.
It would be good if wordwrap is offered for all content.
and ...
I would donate my left kidney for word wrap!
Anyway, if you're mainly editing html, you're in luck - just use the Elements panel instead of the Sources panel. Unfortunately, most of my editing is with JS.
So I'll open a new issue in Chromium and post a link back here, in case anyone wants to support it.
The { } in the footer while on the Network > Response tab worked beautifully to wrap my HTML.\KimBley
In Chrome's Issue 167287: Feature request: word wrap for sources panel, developers said:
[Oct 13, 2014]
We depend heavily here on codemirror capabilities.
Upstream bug: https://github.com/codemirror/CodeMirror/issues/1356
and:
[Dec 14, 2017]
I am a bit scared of the performance concerns of this. Will revisit when we have a more performant way of displaying large/minified files. [Status: Assigned → WontFix]
However, the actual work to fix that CodeMirror issue was broken down into two pieces, each with it's own bug:
Split measuring of long/huge lines – Issue #1022 (Closed on Jan 27, 2014)
Experiment with a partial algorithm for redrawing lines – Issue #2090 (still open, but sounds as though it applies regardless of word-wrap?)
So, they're worried that wrapping super-long lines would grind the editor to a halt. If you can convince them otherwise, with or without actually improving CodeMirror, they would probably be willing to add an option for wrapping in the Sources tab.
So go mess around with:
https://github.com/codemirror/CodeMirror
https://github.com/ChromeDevTools/devtools-frontend
I captured a screenshot just for clarify the "Pretty Print" option at the bottom!