| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
v40 bytecode interpreter is official as of freetype 2.7.
The results don't look so good at the moment. The text looks and glyph
positioning seem worse than they were with the previous v35 interpreter.
So, in the meantime we'll keep using v35, just so everything looks
normal again.
Although the v40 is relevant since around 2.6.3, I rather not do any
FREETYPE_MINOR checks in this patch, because distributions might ship
previous versions with the other (v38) interpreter enabled.
|
|
|
|
|
| |
Cut/Copy/Paste is the standard order most other places.
@fix
|
|
|
|
|
|
| |
Efl_Future actually work with weak reference. So you do not need to
set things to NULL, but you actually need to register the memory location
of the future with efl_future_use.
|
|
|
|
|
|
|
| |
This reverts commit 1881b0d34302b8c29d4b086715eeda9e576ee60a.
This is called from an array constructed with pre-processor macros and
I didn't notice.
|
|
|
|
|
| |
Use the relatively new buffer release API to free up buffers instead
of immediately going nuclear and blowing away all buffer ages.
|
|
|
|
|
|
| |
Oops, I cut and paste it from a wrong file.
Thanks to Vincent Torri for the quick catch.
|
| |
|
|
|
|
|
| |
We may have a few conditionals around that think this has actually been
set at some point, let's surprise them by actually doing that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CPUs can be turned off after boot leading to a sparse mapping of core ids.
For example, if I turn off the first four cores on an exynos 5422 (these
are the low speed cores) then the high speed cores are still numbered 4-7
but there are only 4 cores present.
In that situation using affinity_core % num_cpus will prevent ever being
able to set affinity at all.
Just remove the pointless check and let the user set whatever core id they
want.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We've been pinning the render thread for every EFL process to core 0.
This is a bit silly in the first place, but some big.LITTLE arm systems,
such as exynos 5422, have the LITTLE cores first.
On those systems we put all the render threads on a slow core.
This attempts to fix that by using a random core from the pool of fast
cores.
If we can't determine which cores are fast (ie: we're not on a
linux kernel with cpufreq enabled) then we'll continue doing what we've
always done.
|
|
|
|
|
|
|
|
|
|
| |
In a big.LITTLE ARM system cores can have different capabilities. This
gives an internal API that randomly returns the core id of any of the
system's fastest cores.
On systems where all cores are the same, it will return any available core.
If we don't have cpufreq support we just return 0
|
|
|
|
|
|
|
| |
Without calling eina_cpu_init() the eina_cpu_features bits aren't
properly set up.
Let's call it and see if anything exciting happens.
|
|
|
|
|
|
|
|
|
|
|
|
| |
With MSYS1 or cygwin 1.5, or DOS console, the display is done by redirecting
stdout and al. So to change the colors, the Win32 API of the console must be
used.
On the contrary, the terminals based on mintty (like cygwin 1.8 terminal or MSYS2)
the redirection is done with pipes, so the Win32 API of the console does not
work when changing the colors and we can use the POSIX colors of printf.
This patch is fixing the eina code which alwayss use the Win32 API of the console
on Windows, even if mintty-based terminals are used
|
|
|
|
|
|
| |
use the efl_io_closer_close_on_exec_set() to use a simple boolean
instead of a flag that may be undefined on some platforms, such as
windows.
|
|
|
|
|
|
|
| |
To avoid many ifdef, define the flag to 0 so we "| 0" or "& ~0", that
have no effect.
Fixes T4612.
|
|
|
|
|
|
|
|
|
| |
whenan eoid lookup fails, now print a lot of information on the issue
like the actual id, generation of the id, if its a class or object
(the class bit), if its ref or super bit is set, the actual id (which
includes the table heirachy), which thread id it is, what domain the
object id is and the current and local domains as well as what domains
are mapped in.
|
|
|
|
| |
git rebase.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This would have forced who ever used future,none signal to manually
filter out event triggered by all the future beeing fullfiled and
disconnecting once they receive a value or are marked failed.
|
|
|
|
|
|
|
|
|
| |
Some legacy functions that works with string paths were not redirecting for
the correct code when called with Elm.Fileselector.Button or
Elm.Fileselector.Entry.
This commit fixes this problem.
@fix
|
|
|
|
|
|
|
|
|
|
| |
Fileselector test was waiting for the wrong event. It caused the test to
fail in some situations, since it could check the object when it is
not ready.
Fix T4502
@fix
|
|
|
|
| |
image openning.
|
| |
|
|
|
|
|
| |
Another set of new files which have not been referenced and thus never put into
dist.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed in the mailing list, many people will use worker threads
to execute blocking syscalls and mandating ecore_thread_check() for
voluntary preemption reduces the ecore_thread usefulness a lot.
A clear example is ecore_con usage of connect() and getaddrinfo() in
threads. If the connect timeout expires, the thread will be cancelled,
but it was blocked on syscalls and they will hang around for long
time. If the application exits, ecore will print an error saying it
can SEGV.
Then enable access to pthread_setcancelstate(PTHREAD_CANCEL_ENABLE)
via eina_thread_cancellable_set(EINA_TRUE), to pthread_cancel() via
eina_thread_cancel(), to pthread_cleanup_push()/pthread_cleanup_pop()
via EINA_THREAD_CLEANUP_PUSH()/EINA_THREAD_CLEANUP_POP() and so on.
Ecore threads will enforce non-cancellable threads on its own code,
but the user may decide to enable that and allow cancellation, that's
not an issue since ecore_thread now plays well and use cleanup
functions.
Ecore con connect/resolve make use of that and enable cancellable
state, efl_net_dialer_tcp benefits a lot from that.
A good comparison of the benefit is to run:
./src/examples/ecore/efl_io_copier_example tcp://google.com:1234 :stdout:
before and after. It will timeout after 30s and with this patch the
thread is gone, no ecore error is printed about possible SEGV.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
i wasn't aware of efl_loop_timeout for one-shot timeout promises, then
use it instead of a full object.
|
|
|
|
|
|
| |
functions
Signed-off-by: Chris Michael <cp.michael@samsung.com>
|
|
|
|
| |
Signed-off-by: Chris Michael <cp.michael@samsung.com>
|
|
|
|
| |
The tmp dir is not always /tmp.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Added new test suite for eio eet module
Signed-off-by: Vivek Ellur <vivek.ellur@samsung.com>
Reviewers: cedric
Subscribers: stefan_schmidt, jpeg, cedric
Tags: #efl
Differential Revision: https://phab.enlightenment.org/D3316
|
|
|
|
| |
Initialize temporary index not to cause memory overflow on svg loader.
|
|
|
|
|
| |
Build failed after b5456893ee8a1a86a9b7e0342f644f3785711e06 due to
a missing header.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: @fix
Reviewers: cedric, raster, Hermet
Reviewed By: Hermet
Subscribers: artem.popov, jpeg
Differential Revision: https://phab.enlightenment.org/D4293
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
There is a bug. when calendar showing very first time.
the some of the headers(weekday name) is blank.
Because of elm_layout_text_set() called with NULL value.
Need to insert all of the weekday names before set text.
@fix
Test Plan:
Execute elementary_test
Open calendar sample.
See the all of the header names there.
Reviewers: cedric, jpeg, Hermet
Reviewed By: Hermet
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D4290
|
| |
|
|
|
|
|
| |
This should when done enable the possibility for multi screen in wayland
along with remote display, wireless display and screencasting.
|